> ## Documentation Index
> Fetch the complete documentation index at: https://docs.shiftupai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure and use the ShiftUp Account form

> Choose the fields sellers fill in while keeping Account creation at strategy activation.

The **Customizable Account creation form** lets sellers enter standard and custom Account fields while reviewing a Pipeline agent strategy. Completing the form saves a **draft**. The Salesforce Account is created later, when the strategy is activated.

For a comparison with the screen flow and an explanation of Before Create, start with [How Account creation works in Pipeline agents](https://docs.shiftupai.com/product/pipeline-account-creation.md).

## Enable the customizable form

Use a **ShiftUp Admin** account and confirm sellers have access to the Account fields you want them to fill in.

1. Open **ShiftUp Admin → Advanced → App Settings**.
2. Find **Pipeline Agents & Workspace**.
3. Leave **Enable Account Creation Flow** off. If it is on, sellers get the screen flow instead.
4. Turn on **Enable customizable Account creation form**.

The **Account form fields** editor is directly below the customizable-form setting. Use it to choose the fields and their display order.

## Add and arrange fields

1. Under **Account form fields**, use **Find an Account field** to search by label or API name.
2. Select the field in **Account field**, then click **Add field**.
3. Set its **Order**. Lower numbers appear first; using `10`, `20`, and `30` leaves room to insert fields later.
4. Repeat for the other fields you need.
5. Click **Save fields** and wait for **Account form fields saved.** before checking the seller's form.

For a new custom field, create it first under **Salesforce Setup → Object Manager → Account → Fields & Relationships → New**, grant the appropriate field access, then return to App Settings and select **Reload saved fields** to refresh the available fields. Reloading also replaces unsaved field-list edits with the saved configuration.

### Example: collect Account Number and Type

Add these existing Salesforce fields:

| Field | Example order |
| - | - |
| **Account Number** | `10` |
| **Type** | `20` |

The seller sees required inputs first, followed by your selected fields in order. They can enter `ACME-001` as the Account Number and select a Type allowed in your org. Adding these fields to the list makes them available on the form; it does not, by itself, make optional fields required.

### What controls the fields sellers see?

* **Required fields come first.** Required Account fields and required inputs for the seller's selected layout are included before your configured fields. An empty field list still shows required inputs.
* **Access still applies.** The form omits fields the seller cannot read or fill when creating an Account. Calculated and system-managed fields are not choices for editable inputs.
* **Record types and picklists follow Salesforce.** Sellers can choose permitted record types when applicable, and picklist options follow that choice. A dependent picklist includes its controlling field.
* **Your Account page layout is not copied into this form.** Use **Account form fields** to select optional inputs.
* **Owner and parent are handled by the Pipeline activation process.** They are not extra fields to configure on this draft form.

The org-wide **Disable account field auto-fill** setting controls whether supported company facts fill empty fields. Sellers' saved answers are retained. Adding a custom field does not make ShiftUp research a value for it automatically.

## Use the form as a seller

1. In a Pipeline agent's **Agent results**, open the strategy's **Account choice**.
2. Search for an existing Account first. If none fits, select **Create new account**.
3. Review the available company details, choose a record type if offered, and complete the fields.
4. Click **Save account details**. This saves the draft; it does not create a Salesforce Account.
5. When ready, select **Activate**. ShiftUp creates the new Account using the draft and continues with strategy creation.

Cancelling the form creates nothing. Choosing **Create new account** again lets the seller return to the saved draft details.

## Required inputs, validation rules, and defaults

The form checks required inputs before accepting the details. **Salesforce Account validation rules run when the Account is saved during activation**, so successfully saving a draft does not guarantee that activation can create the Account.

Use **ShiftUp Pipeline Account Before Create** to supply additional field values automatically during activation. It works with both the short and customizable ShiftUp forms. It has no screen and does not create the record itself. See [Set defaults with the Before Create flow](https://docs.shiftupai.com/customize-accounts-created-by-pipeline-agents.md).

If sellers need custom validation messages, conditional screens, or to resolve Salesforce save errors before activation, use the [Account creation screen flow](https://docs.shiftupai.com/how-to/account-creation-screen-flow.md). That option creates the Account immediately.

## Check the setup

Try the form in a sandbox with a seller's permissions:

1. Confirm **Account Number** and **Type** appear, with required fields first.
2. Save `ACME-001` in the draft and reopen the form to check the saved value.
3. Confirm saving the draft has not created the Account.
4. Activate the strategy, then check the created Account's values and any defaults supplied by your Before Create override.

If a field is missing, check seller access, whether it is eligible for Account creation, and whether the field configuration finished saving. If the wrong form opens, check both settings in the [overview's settings table](https://docs.shiftupai.com/product/pipeline-account-creation.md#which-setting-chooses-the-form).

To return to the short form, turn **Enable customizable Account creation form** off while leaving **Enable Account Creation Flow** off. The short form collects Name, Website, and Industry, and creation still happens at activation.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.