# Lever for Docusign IAM

> Connect Lever to your Docusign agreement workflows. Read candidate and job posting data to pre-fill offer letters, write the outcome back to the candidate, and attach the signed document to their Files tab in Lever.

- Web page: https://fluidlabs.com/documentation/lever-for-docusign
- Published by: Fluidlabs
- Status: Live on the Docusign App Center
- Docusign App Center listing: https://apps.docusign.com/app-center/app/a7d473cd-c940-46b9-b073-6a5db78f3607
- App page: https://fluidlabs.com/integrations/lever-for-docusign
- Last updated: 2026-09-10
- Support: docusign-support@fluidlabs.com

## Contents

- [Quick Start](https://fluidlabs.com/documentation/lever-for-docusign#1-quick-start)
- [Implementation Guide & Known Behaviors](https://fluidlabs.com/documentation/lever-for-docusign#2-implementation-guide--known-behaviors)
- [Installation and Configuration](https://fluidlabs.com/documentation/lever-for-docusign#3-installation-and-configuration)
- [How to Use the App](https://fluidlabs.com/documentation/lever-for-docusign#4-how-to-use-the-app)
- [Read from Lever](https://fluidlabs.com/documentation/lever-for-docusign#5-read-from-lever)
- [Writeback to Lever](https://fluidlabs.com/documentation/lever-for-docusign#6-writeback-to-lever)
- [File Upload to Lever](https://fluidlabs.com/documentation/lever-for-docusign#7-file-upload-to-lever)
- [FAQ & Troubleshooting](https://fluidlabs.com/documentation/lever-for-docusign#8-faq--troubleshooting)

---

## 1. Quick Start

### 1. Install the App

- Open the [**Docusign App Center**](https://apps.docusign.com/app-center/extensionapps) and search for **Lever**.
- Open the **Lever** app card, click **Install App**, then **Install and Authorize** on the consent screen.

### 2. Create a Connection

- On the installed app page, click **Connect Account**.
- Choose the connection visibility (**Private** or **Shared**), give the connection a name, and click **Log In**.
- Sign in to Lever, then click **Accept** on the Lever consent screen.

### 3. Create a Workflow

- In Docusign, open **Workflow Manager** and create a workflow.
- Choose your preferred workflow start type.
- Add a Lever step: **Read**, **Writeback**, or **File Upload**.

### 4. Available Actions

- [**Read from Lever**](https://fluidlabs.com/documentation/lever-for-docusign#5-read-from-lever): pull a Candidate or Job Posting into your workflow to pre-fill an offer letter.
- [**Writeback to Lever**](https://fluidlabs.com/documentation/lever-for-docusign#6-writeback-to-lever): update a candidate, create a new one, or add a note.
- [**File Upload to Lever**](https://fluidlabs.com/documentation/lever-for-docusign#7-file-upload-to-lever): attach the signed document to the candidate's Files tab.

### 5. Key Things to Know

A candidate is an application, not a person. Someone who applied to two jobs is two candidate records with the same name and email. See [Candidates are applications](https://fluidlabs.com/documentation/lever-for-docusign#2-implementation-guide--known-behaviors).


## 2. Implementation Guide & Known Behaviors

The Read step covers two objects: `Candidate` with 22 fields and `Job Posting` with 21. After a change to the Lever fields, for example a new field, run **Reconnect** under **Manage Connections** to make sure the step has the latest catalog.

A candidate is one application, not a person. Someone who applied to two jobs is two candidate records: same Name and Email Addresses, different Record ID, Stage and Job Posting Title.

### Writeback Behaviors

#### Scope of an update

| Fields | Scope |
| --- | --- |
| Name, Headline, Location, Email Addresses, Phone Numbers, Mobile / Work / Home Phone, Links | Changes on every application this person holds. |
| Stage, Tags | Only changes on the current application. |

#### What an update does to each field

| Field | Behavior on update |
| --- | --- |
| Email Addresses | Adds to the existing list. Case-insensitive, so an address already on the record is not duplicated. |
| Phone Numbers | Adds a number to the existing list if it is not already there. The number lands with no type, which Lever shows as **Other**. |
| Mobile / Work / Home Phone | Replaces the first number of that type. A candidate with three mobile numbers shows and updates only the first. |
| Links, Tags | Adds to the existing list. |
| Name, Headline, Location, Stage | Replaces the current value. |

An update never removes a value. You cannot drop an email address, phone number, tag, or link from a workflow.

#### Individual fields

| Field | What to know |
| --- | --- |
| Name | Required on every write. To change a name the candidate already has, tick **Overwrite if field value exists**. |
| Location | Stored as Lever's own version of the string: `Houston, TX, USA` reads back as `Houston, Texas, USA`. |

#### Creating a candidate

An empty Record ID under **Update or Create** creates a candidate. An email address that already belongs to a contact attaches the new application to that person and keeps their existing name. With **Create** as the write setting, Job Posting Title is also available: map it to attach the new application to a job, otherwise the candidate is created with no job selected.

#### Notes

The `Note` object is create-only and has two fields, Candidate Record ID and Note Content. Both are required. A Note writeback puts the note's Record ID into the variable picker, not the candidate's. Do not use it for File Upload.

> ⚠️ Address the candidate by Record ID, for example from the Read step.

### Searching for a Record

Record ID is the only key that guarantees one match. Without it, narrow the rule to a single application: Email Addresses plus Job Posting Title, Stage, or Tags.

#### Searchable fields

Their labels carry a **(searchable)** suffix in the picker.

**Candidate:** Record ID, Email Addresses, Tags, Sources, Origin, Stage, Job Posting Title.

**Job Posting:** Record ID, Job Title, State, Team, Location, Work type, Tags.

Any other field in the rule stops the step.

#### Matching

- **Record ID overrides every other condition.** When the rule has a Record ID, the other conditions are not applied. Leave it out when the other conditions should decide.
- **Tags and Sources take several values separated by `;`, and the record has to carry all of them.** `Tags = "Java; Kubernetes"` finds candidates tagged with both. Two conditions on Tags mean the same thing. One value that matches nothing empties the result.
- **Every other field takes one value.** A `;` in it, or a second condition on the same field, stops the step.
- **Stage, Job Posting Title, Job Title, Origin and State ignore case and extra spaces.** Tags, Sources, Team, Location and Work type are case sensitive: `Team = Customer Success` matches, `customer success` returns nothing. Use values as the Read step returns them.
- **A wrong Stage, Job Posting Title, Job Title, Origin or State stops the step.** A wrong value in any other field returns an empty result.

| Field | What to know |
| --- | --- |
| Record ID | Returns a single record. An empty value returns nothing. |
| Email Addresses | Returns every application this person holds. |
| Tags | Case sensitive. Matches the posting's automatic tags as well as the ones a recruiter set. |
| Sources | Matches whole values, not parts of them. |
| Origin | One of `agency`, `applied`, `internal`, `referred`, `sourced`, `university`, in any letter case. |
| State | One of `published`, `internal`, `closed`, `draft`, `pending`, `rejected`, in any letter case. |
| Stage | The stage name as shown in Lever. |
| Job Posting Title, Job Title | The job title as shown in Lever. Two postings with the same title stop the step. |
| Location | The value the Read step returns, `Remote - US`, not the longer string in the posting form. |

> ⚠️ An email search returns every application the person holds. Add Job Posting Title, Stage, or a Tag to the rule to land on one.

### Reading Record Data

Tags include the posting's title, team, and location, which Lever adds to every application and hides on the candidate profile. A candidate tagged `qa-keep` on a Customer Success Manager posting returns:

```
Customer Success Manager; Customer Success; Remote - US; qa-keep
```

#### Formats

| Type | Reads as |
| --- | --- |
| Date | ISO instant: `2026-08-15T19:28:44.551Z` |
| List | Email Addresses, Phone Numbers, Links, Tags, Sources: one string with `; ` between values, `Product Manager, Growth; Remote - US` |

#### Job Posting

Department stays empty unless your Lever account uses departments. Team is populated either way.

Posting URL and Apply URL are two different links: the public job page and the application page.

### Field Values Reference

Values must match your Lever account exactly.

| Field | Accepted values |
| --- | --- |
| Origin | `agency`, `applied`, `internal`, `referred`, `sourced`, `university`. Any letter case. |
| Location type | `remote`, `onsite`, `hybrid`. Read only. |
| State | `published`, `internal`, `closed`, `draft`, `pending`, `rejected`. Any letter case. Read only. |
| Salary Interval | A machine value such as `per-year-salary`, not the `/ year` shown in Lever. Read only. |
| Stage, Work type, Team, Location | Configured in your Lever account, so the values are your own. Use them as the Read step returns them. |


## 3. Installation and Configuration

### Prerequisites

- A **Lever** account with permission to authorize integrations.
- A **Docusign** account with admin rights to install and manage apps in the App Center.

### How to Install the App

- Open the [**Docusign App Center**](https://apps.docusign.com/app-center/extensionapps) and search for **Lever** in the search bar.

  ![Docusign App Center search results showing the Lever extension app by Fluidlabs.](https://fluidlabs.com/images/documentation/lever-for-docusign/app-center-search.webp)

- Click the **Lever** app card to open its detail page, then click **Install App**.

  ![The Lever app page in the Docusign App Center with the Install App button.](https://fluidlabs.com/images/documentation/lever-for-docusign/app-install.webp)

- Review the access the app requests and click **Install and Authorize**.

  ![The Install and authorize Lever app screen listing the requested access, with the Install and Authorize button.](https://fluidlabs.com/images/documentation/lever-for-docusign/install-authorize.webp)

The app now appears with an **Installed** status.

### Connecting Your Account

- On the installed app page, click **Connect Account**.

  ![The installed Lever app page showing the Connect Account button.](https://fluidlabs.com/images/documentation/lever-for-docusign/connect-account.webp)

- **Connection Visibility**: choose how the connection is shared:

  - **Private**: accessible only by you in Docusign.
  - **Shared**: accessible by multiple users or the whole team.

  ![The Connection Visibility step with Private and Shared options; Shared is selected.](https://fluidlabs.com/images/documentation/lever-for-docusign/connection-visibility.webp)

- **Name Connection**: enter a name. It appears in workflow steps, so make it easy to identify. Click **Log In**.

  ![The Name Connection step with the name Demo Guide entered.](https://fluidlabs.com/images/documentation/lever-for-docusign/name-connection.webp)

- Sign in to Lever if you are not signed in already. Lever names the app **Docusign IAM for Lever**.

  ![The Lever sign-in page with email and password fields and options to continue with Google, Microsoft, or SSO.](https://fluidlabs.com/images/documentation/lever-for-docusign/lever-login.webp)

- On the Lever consent screen, click **Accept**.

  ![The Lever Authorize App screen listing the access Docusign IAM for Lever requests, with Decline and Accept buttons.](https://fluidlabs.com/images/documentation/lever-for-docusign/lever-consent-authorize.webp)

The connection is added and ready to use in workflow steps.

> The Lever consent screen appears every time you create a connection.

### Managing Connections

On the Lever app page, open the **Manage** dropdown.

![The Manage dropdown on the Lever app page showing New Connection, Manage Connections, Manage Apps, and Uninstall App.](https://fluidlabs.com/images/documentation/lever-for-docusign/manage-connections-menu.webp)

Select **Manage Connections** to see every connection.

![The Lever connections list showing one shared connection with an Active status and the New Connection button.](https://fluidlabs.com/images/documentation/lever-for-docusign/connections-list.webp)

Use the three-dot (⋮) menu next to a connection:

![The Lever connections list with the three-dot menu open showing Edit connection name, Reconnect, Reload Objects, and Delete Connection.](https://fluidlabs.com/images/documentation/lever-for-docusign/connections-actions-menu.webp)

- **Edit connection name**: rename the connection.
- **Reconnect**: refresh the connection. Run this once after an app update that changes its fields or objects.
- **Reload Objects**: refresh the available record types and fields.
- **Delete Connection**: remove the connection. ⚠️ This may break workflows that use it.

### Adding a New Connection

Use **Manage → New Connection** on the app page, or **+ New Connection** on the Connections page. Each connection appears separately in workflow steps.

### Revoking Access from Lever

In Lever, open **Settings → Integrations and API → Authorized Apps** and revoke **Docusign IAM for Lever**. That stops every Docusign connection created by that Lever user.


## 4. How to Use the App

### Create a Workflow

- Log in to Docusign and go to **Agreements → Workflows**.
- Click **Create Workflow**.

  ![The Docusign Workflows screen showing existing workflows and the Create Workflow button.](https://fluidlabs.com/images/documentation/lever-for-docusign/workflow.webp)

- Build your workflow using the available steps, including the Lever actions.
- Publish the workflow when it is ready.

### Available Lever Actions

Click **+ Add Step** and search for **Lever**:

![The Add New Step dialog with "Lever" searched, showing File Upload to Lever, Writeback to Lever, and Read from Lever.](https://fluidlabs.com/images/documentation/lever-for-docusign/add-step-actions.webp)

- **Read from Lever**: fetch a **Candidate** or **Job Posting** and expose its fields as workflow variables. See [Read from Lever](https://fluidlabs.com/documentation/lever-for-docusign#5-read-from-lever).
- **Writeback to Lever**: update or create a **Candidate**, or create a **Note** on one. See [Writeback to Lever](https://fluidlabs.com/documentation/lever-for-docusign#6-writeback-to-lever).
- **File Upload to Lever**: store a document from the workflow on a candidate's Files tab. See [File Upload to Lever](https://fluidlabs.com/documentation/lever-for-docusign#7-file-upload-to-lever).

A typical hiring flow:

1. **Read from Lever**: find the candidate.
2. **Prepare eSignature Template**: pre-fill the offer letter.
3. **Send Documents for Signature**.
4. **File Upload to Lever**: attach the signed offer to the candidate.
5. **Writeback to Lever**: move the stage, add a tag, or post a note.

Job postings are read-only. There is no writeback to a posting.


## 5. Read from Lever

The **Read from Lever** step retrieves a record and exposes its fields as workflow variables.

### Start the Workflow From an API Call

In this example the workflow starts **From an API Call** and receives the ID of the record to read.

On the workflow canvas, click **Add workflow start**.

![The empty workflow canvas with the Add workflow start button.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-add-workflow-start-canvas.webp)

- **Select a method**: choose **From an API Call**.

  ![The Add workflow start panel with From an API Call selected as the method.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-workflow-start-method.webp)

- **Set up variables**: add a **Text** variable named `object_id`.

  ![The variables step with a Text variable named object_id.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-workflow-start-variable.webp)

- **Process type**: choose **Automated process**.

  ![The process-type step with Automated process selected.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-workflow-start-process.webp)

Once published, the workflow has a URL your external system calls, passing `object_id`.

### 1. Add the Read Step

On the workflow canvas, click **+ Add a step** below **Start Workflow**.

![The workflow canvas with the Add a step button below the From an API call start.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-add-step-canvas.webp)

Search for **Lever** and select **Read from Lever**.

![The Add New Step dialog with Read from Lever highlighted.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-add-step-search.webp)

### 2. Configure Connection and Object

- **Connection**: select the connection you created during [installation](https://fluidlabs.com/documentation/lever-for-docusign#3-installation-and-configuration).

  ![The Read step Connection dropdown showing the Lever connection.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-configure-connection.webp)

- **Lever object**: choose **Candidate** or **Job Posting**. This example uses **Candidate**.

  ![The Lever object dropdown showing Candidate and Job Posting.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-configure-object.webp)

Click **Next**.

### 3. Select Fields

Click **Add or Remove Fields** and tick the fields your workflow needs. The selected fields become workflow variables for later steps.

![The Fields step with the Add or Remove Fields button and one selected field.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-select-fields.webp)

![The field browser listing Candidate fields with checkboxes.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-fields-browser.webp)

Available fields:

**Candidate:** Record ID, Name, Headline, Email Addresses, First Email, Second Email, Phone Numbers, Mobile Phone, Work Phone, Home Phone, Location, Links, Tags, Sources, Origin, Stage, Owner Email, Owner Name, Job Posting Title, Lever Profile URL, Created At, Last Interaction At.

**Job Posting:** Record ID, Job Title, State, Team, Department, Location, Work type, Location type, Tags, Posting Owner Name, Posting Owner Email, Hiring Manager Name, Hiring Manager Email, Salary Range Minimum, Salary Range Maximum, Salary Currency, Salary Interval, Salary Description, Posting URL, Apply URL, Created At.

Fields with a fixed set of values are listed under [Field Values Reference](https://fluidlabs.com/documentation/lever-for-docusign#2-implementation-guide--known-behaviors).

Click **Next**.

### 4. Identify the Record

Create a rule that tells the step which record to read. In this example, match the Lever **Record ID** to the `object_id` variable from the workflow start:

- **Lever field:** Record ID
- **Operator:** Equal to
- **Workflow field:** `object_id`

![The record-matching rule: Record ID equals object_id, with A single record selected.](https://fluidlabs.com/images/documentation/lever-for-docusign/read-identify-record.webp)

Under **How many records should this step return?**, pick one:

- **A single record**: the first record that matches.
- **Multiple records**: up to five, in an order Lever does not guarantee.

Use **preview this step** to check the rule against live data. Click **Apply**.

Searchable fields are Record ID, Email Addresses, Tags, Sources, Origin, Stage, and Job Posting Title for a candidate, and Record ID, Job Title, State, Team, Location, Work type, and Tags for a job posting. Every other field stops the step. How each field matches is under [Searching for a Record](https://fluidlabs.com/documentation/lever-for-docusign#2-implementation-guide--known-behaviors).


## 6. Writeback to Lever

The **Writeback to Lever** step updates a candidate, creates one, or posts a note.

Check [what an update does to each field](https://fluidlabs.com/documentation/lever-for-docusign#2-implementation-guide--known-behaviors) first: some fields replace their value and some add to a list.

### 1. Add the Writeback Step

On the workflow canvas, click **+ Add a step** where the writeback belongs, for example below a **Collect Data with Web Forms** step.

![The workflow canvas with the Add a step button below a Collect Data with Web Forms step.](https://fluidlabs.com/images/documentation/lever-for-docusign/writeback-add-step-canvas.webp)

Search for **Lever** and select **Writeback to Lever**.

![The Add New Step dialog with Writeback to Lever highlighted.](https://fluidlabs.com/images/documentation/lever-for-docusign/writeback-add-step-search.webp)

### 2. Configure Connection, Object, and Write Setting

- **Connection**: select your Lever connection.

- **Lever object**: choose **Candidate** or **Note**. This walkthrough uses Candidate.

  ![The Lever object dropdown for the Writeback step showing Candidate and Note.](https://fluidlabs.com/images/documentation/lever-for-docusign/writeback-configure-object.webp)

- **Write settings**:

  - **Update or Create**: updates the matching candidate, or creates one if the match rule finds nothing.
  - **Update**: updates an existing candidate only.
  - **Create**: always creates a candidate.

  ![The Write settings options: Update or Create, Update, and Create.](https://fluidlabs.com/images/documentation/lever-for-docusign/writeback-write-settings.webp)

Click **Next**.

### 3. Map Fields

Click **Add or Remove Fields** and tick the fields you want to write.

![The field browser listing the eleven writable Candidate fields with checkboxes.](https://fluidlabs.com/images/documentation/lever-for-docusign/writeback-fields-browser.webp)

Each selected field then gets its own row. Map it to the workflow variable that supplies the value.

![The Writeback step with Name, Email Addresses, Mobile Phone, Work Phone, Home Phone, and Location each mapped to a variable.](https://fluidlabs.com/images/documentation/lever-for-docusign/writeback-map-fields.webp)

**Writable Candidate fields:** Name\*, Headline, Email Addresses, Phone Numbers, Mobile Phone, Work Phone, Home Phone, Location, Links, Tags, Stage.

_\* Name is a required field. To change a name the candidate already has, tick **Overwrite if field value exists** on it._

With **Create** as the write setting, Job Posting Title is also available: map it to attach the new candidate to a job.

⚠️ **Map from the right source.** The variable picker also lists the output of your **Read from Lever** step. Mapping from there writes the original values back unchanged. Map from the step that collected the new data, such as **Collect Data with Web Forms**.

Click **Next**.

### 4. Identify the Record

Address the candidate by Record ID, for example from the Read step.

- **Lever field:** Record ID
- **Operator:** Equal to
- **Workflow field:** the Record ID from your Read step

![The record-matching rule for Writeback: Record ID equals the Record ID variable.](https://fluidlabs.com/images/documentation/lever-for-docusign/writeback-identify-record.webp)

Click **Apply**.

Leaving the Record ID empty under **Update or Create** creates a candidate.

### Writing a Note

Select **Note** as the Lever object.

![The Lever object dropdown with Note selected.](https://fluidlabs.com/images/documentation/lever-for-docusign/note-object.webp)

**Create** is the only write setting.

![The Note object with Create as the only write setting.](https://fluidlabs.com/images/documentation/lever-for-docusign/note-write-settings.webp)

Map both required fields, **Candidate Record ID** and **Note Content**.

![The Note fields: Candidate Record ID and Note Content, both required.](https://fluidlabs.com/images/documentation/lever-for-docusign/note-fields.webp)

The Record ID this step returns belongs to the note. For a File Upload later in the workflow, keep using the candidate's Record ID from the Read step.


## 7. File Upload to Lever

The **File Upload to Lever** step attaches a document produced earlier in the workflow to a candidate's **Files** tab. Maximum size is 30 MB.

### 1. Add the File Upload Step

Add a step after signing completes, search for **Lever**, and select **File Upload to Lever**.

![The Add New Step dialog with File Upload to Lever highlighted.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-add-step-search.webp)

### 2. Select the File

Choose the file or envelope from an earlier step. In this example it is the **Combined Envelope File** from **Send Documents for Signature**.

![The file picker showing Combined Envelope File and Envelope Info under Send Documents for Signature.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-select-file.webp)

> An empty list means no earlier step in the workflow produced a file.

### 3. Choose the Location

- **Select connection**: your Lever connection.

  ![The File Upload connection dropdown showing the Lever connection.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-select-connection.webp)

- **Select drive**: **Candidates** is the only drive.

  ![The Select drive dropdown with the Candidates option.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-select-drive.webp)

- Click **Add Folder**.

  ![The File Upload step with the Candidates drive selected and the Add Folder button.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-add-folder.webp)

### 4. Point the Folder at the Candidate

The folder holds the candidate's Record ID. Lever creates no folder.

- Open the **Select folder** dropdown and pick **New Subfolder**.

  ![The Select folder dropdown open with the New Subfolder option highlighted.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-new-subfolder.webp)

- In the **New folder** dialog, click **Add Variable**.

  ![The New folder dialog with Add Variable and Add Text buttons and an empty Folder name field.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-new-folder-dialog.webp)

- Choose the step that returns the candidate, then select **Record ID** and click **Add**. A Read from Lever or a Candidate Writeback step returns the candidate's Record ID; a Note step returns the note's.

  ![The variable picker showing the Read from Lever step with Record ID under Suggested.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-add-variable-record-id.webp)

- The variable appears in the **Folder name** field.

  ![The New folder dialog with a Record ID variable in the Folder name field and the Add button.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-folder-name-chip.webp)

- **Select folder** now shows the Record ID variable. Click **Next**.

  ![The File Upload location with connection, Candidates drive, and a Record ID variable as the folder.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-location-set.webp)

The app reads the last segment of the path, so a subfolder overrides the folder above it. Plain text in the folder and the Record ID in a subfolder still reaches the right candidate.

![The Select subfolder dropdown open with the New Subfolder option.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-subfolder-dropdown.webp)

![The File Upload location with the text TestFolder as the folder and a Record ID variable as the subfolder.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-folder-placeholder.webp)

We do not recommend it. Put the Record ID in the folder and leave the subfolder out.

### 5. Name the File

Build the file name from **Add Text** and **Add Variable**. A timestamp variable keeps repeat runs from producing identical names.

![The file name step with a text chip and a Start Date and Time variable chip, and the resulting file path.](https://fluidlabs.com/images/documentation/lever-for-docusign/file-upload-file-name.webp)

The app replaces anything outside letters, digits, dots, and hyphens with `_`, so `2026-08-21T08:20:32.706Z` is stored as `2026-08-21T08_20_32.706Z`.

Click **Apply**. The file lands on the candidate's **Files** tab, marked **Related to** their job.


## 8. FAQ & Troubleshooting

**The Lever consent screen appears every time I create a connection.**
> That is how the app connects. Earlier connections stay **Active** under **Manage Connections**.

**A field or a search option I expect is missing from the step.**
> Open **Manage Connections**, click **Reconnect** on the connection, then reopen the step.

**The Read step fails with `Request failed with status code 400`.**
> Check the rule: a field outside the searchable list, a `;` in a field other than Tags or Sources, two conditions on one field other than Tags or Sources, a Stage or Job Posting Title that does not exist in Lever, or an Origin or State outside its list.

**My rule has a Record ID and another condition, and the record comes back even though it does not match the other condition.**
> A Record ID identifies one record, so the other conditions are not applied. Drop the Record ID when the other conditions should decide.

**Why can't I search by name, First Email, or Mobile Phone?**
> Name and phone number are not searchable. First Email, Second Email and Mobile / Work / Home Phone are assembled from the full lists on the record, so they are not searchable either. Search on Email Addresses.

**A tag search returns nothing, but the candidate has the tag.**
> Tag values are case sensitive. Copy the tag as the Read step returns it.

**The Tags variable holds more tags than the candidate profile shows.**
> The posting's title, team, and location are added to every application as tags. See [Reading Record Data](https://fluidlabs.com/documentation/lever-for-docusign#2-implementation-guide--known-behaviors).

**I created a candidate and Lever saved a different name.**
> One of the email addresses already belonged to a contact, so the new application was attached to that person and kept their existing name.

**I wrote a phone number and the old one is still there.**
> Phone Numbers adds to the list. To replace a number, write to Mobile Phone, Work Phone, or Home Phone.

**How do I remove a tag, a link, or an email address?**
> Not from a workflow. Those fields only add. Remove the value in Lever.

**The location I wrote back does not match what the Read step returns.**
> Lever stores its own version of the location, so `Houston, TX, USA` comes back as `Houston, Texas, USA`. Compare against the value the Read step returns.

**I created a candidate and the profile says "No job selected yet".**
> Map Job Posting Title in the Writeback step with **Create** as the write setting. It takes the job title as shown in Lever.

**The file picker says no files are available.**
> No earlier step produced a file. Add the upload after **Send Documents for Signature**.

**The file did not appear on the candidate.**
> The folder has to hold the candidate's Record ID variable, from a step that runs before the upload. A Record ID taken from a Note step is the note's, and no candidate has that ID.

---

Lever for Docusign IAM is published by Fluidlabs. Docusign is a trademark of Docusign, Inc.
