# Configuring Auto-Start Document Workflows

With auto-start document workflows, you can configure Vault to initiate a workflow within an <a href="/en/gr/12399/">entry action</a>
. This configuration supports process automation in a variety of different use cases.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: Auto-start document workflows will show <em>System</em> as the Workflow Owner.</p>
    </div>
  </div>
</div>


 
## Example Usage

Below are possible ways you can use auto-start document workflows:
- When a document enters the _In Review_ state, a configured workflow could automatically assign a _Review_ task to the Editor role.
- When a document workflow is auto-started based on a document state change, the workflow can use Decision and Action steps to evaluate document metadata and automates additional field updates based on the Decision step.

## Eligible Workflows {#eligible}

You can auto-start a document workflow if the following conditions apply:
- **Allow auto-start from entry action** setting (within Workflow Details) must be selected.
- **Use workflow for single document record** setting (within Workflow Details) must be selected.
- Participant control must use the **Use roles as participants**, **Use custom action to define participants**, **Allow workflow task owners to select participants**, **Use user reference field as participant**, or **Use Vault user group as participants** setting.
- **Document Lifecycle** is set to a specific lifecycle and not **Any document** lifecycle
- Start step cannot include controls for **Instructions**, **Date**, **Prompt for Fields**, or **Variable**.

You can find general instructions for workflow setup in <a href="/en/gr/50498/">Configuring Document Workflows</a>
.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If you enable <em>Allow auto-start from entry action</em> before configuring any steps, Vault will filter the steps and settings to only show valid options. If the workflow includes steps or settings that make it ineligible for auto-start, Vault will not allow you to save the workflow with the auto-start option selected.</p>
    </div>
  </div>
</div>



## Defining the Entry Action

You can find general instructions for creating entry actions in <a href="/en/gr/12399/">Defining Document State Entry Actions</a>
.

The **Start Workflow** entry action requires that you select a workflow. Only workflows that are [eligible][6] appear in the list.

## Workflow Errors

If an error prevents Vault from starting the configured workflow when the document changes lifecycle states, Vault will roll back the document state change. Possible error scenarios include:
* If _Allow auto-start from entry action_ is disabled, and the workflow is selected from the Start Workflow entry action, then the workflow cannot activate.
* If _Allow auto-start from entry action_ is enabled, and the Workflow Owner is referenced on a _Task_, _Notification_, or an _Update Sharing Settings_ step, then you cannot save the workflow.
* If _Allow auto-start from entry action_ is enabled, and Allow workflow initiator to select participants is enabled in the Participant Controls, the workflow cannot activate.
*  If _Allow auto-start from entry action_ is enabled, and the document is currently included in over ten active workflows, the workflow cannot activate. This limit does not apply to Read & Understood workflows.

<div class="note-border alert-info">
  <div class="alert alert-info" role="alert">
    <div><i class="far fa-info-circle"></i></div>
    <div class="alert-text">
      <p><strong>Note</strong>: If <em>Allow auto-start form entry action</em> is enabled, you cannot select the Workflow Owner in the <em>Task</em>, <em>Notification</em>, and <em>Update Sharing Setting</em> step.</p>
    </div>
  </div>
</div>



## Auto-Start and Start Next Workflow Enabled

If a document workflow is auto-started due to a state change on the document prior to the workflow ending and _Display start next workflow dialog_ when workflow ends is enabled on the _End_ step, the _Start Next Workflow_ dialog will not display if the workflow contains an active Task step. It will also not display if there's an active task on the document. If the auto-started workflow contains no tasks, but does contain a state change action, the _Start Next Workflow_ dialog will display and include workflow options based on the new document state.

This type of scenario is possible in the following configuration:
- The **Start Workflow** entry action is configured on the _Approved_ state for a document lifecycle
- A workflow for a document in the _Draft_ state is configured with _Display start next workflow dialog when workflow ends_ is configured on the _End_ step
- When the _Draft_ state workflow ends, the user can move the document to the Approved state with the **Start Workflow** entry action configured. If the workflow the entry action will auto-start contains a task, the _Start Next Workflow_ dialog will not display.

[6]: #eligible