---
schema_version: "1"
id: 5d5c16d9b3da1dc9de181b6931d0f7862e51b6c3c587d49431939e0e2dab8a7f
title: Flow Orchestration Interactive Steps
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/orchestrator_concepts_steps_interactive.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.orchestrator_concepts_steps_interactive.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: bef299640c3687b496c950fa4be4d535b4140d0086c98d4ffb34f976cd1148fa
description: An interactive step references an active screen flow and generates an orchestration work item. An assigned user completes the active screen flow in the Flow Orchestration Work Guide on the related record page. You can control when an interactive step is ready to start or when its status is set to completed. All interactive steps are processed asynchronously.
products:
  - Flow Builder
  - Salesforce Platform
release: "264"
---
# Flow Orchestration Interactive Steps

An interactive step references an active screen flow and generates an orchestration work item. An assigned user completes the active screen flow in the Flow Orchestration Work Guide on the related record page. You can control when an interactive step is ready to start or when its status is set to completed. All interactive steps are processed asynchronously.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=platform.automate_orchestrator_about_supported_editions.htm&amp;release=264.0.0&amp;type=5" title="Review the supported products and editions for Flow Orchestration.">View supported editions for Flow Orchestration.</a></td></tr></tbody></table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/images/icon_note.png)

Note The Step resource in Flow Orchestration isn't related to the discontinued Step element in flows.

## Interactive Step Work Cycle

![The workflow for an interactive step in an orchestration](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-platform-platform_automation-264-0-0-production-enus/60568438-ec7e-4665-acd1-7c80dcbe60d5/platform_automation/images/orchestration/orchestrator_interactive_step_work_cycle.png)

For flows running in version 57.0 and earlier, after an interactive step is marked as complete, an orchestration run resumes in the context of the user who completed the associated work item. If the person who completed a work item has granular access to specific flows without the Run Flows permission, the orchestration run can't resume. To resume the orchestration, someone with the Run Flows permission can run another work item or an admin can trigger a Flow Orchestration Event with the ID of the paused orchestration run.

## When to Start the Step

To control when an interactive step starts, select a condition.

 
| Step Condition | Requires |
| --- | --- |
| **When the stage starts, the step starts** | — |
| **When another step is marked Completed, the step starts** | The name of the step that must be completed before the step can start |
| **When the specified requirements are met, the step starts** | Up to 10 requirements that determine whether the step can start |
| **When the specified evaluation flow returns True, the step starts** | The name of the active evaluation flow that determines whether the step can start |

## When to Complete the Step

To control when an interactive step completes, select a condition.

 
| Step Condition | Requires |
| --- | --- |
| **When the assigned user has completed the screen flow, the step is marked Completed** | — |
| **When the specified requirements are met, the step is marked Completed** | Up to 10 requirements that determine whether the step can be completed |
| **When the specified evaluation flow returns True, the step is marked Completed** | The name of the evaluation flow that determines whether the step can be completed |

## Who Completes the Step

When an orchestration is designed, an interactive step is assigned to a user, group, or queue.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small " summary="Step Assignees">
        <caption>Step Assignees</caption>
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d111619e252">Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d111619e255">Description</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e252 ">User</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e255 ">
              <ul>
                <li>The username of an internal user</li>

                <li>The username of a credentialed Experience Cloud site visitor</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e252 ">Group</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e255 ">
              <ul>
                <li>The API name of a group that includes only internal users</li>

                <li>The API name of a group that includes only credentialed Aura site
                  visitors</li>

                <li>The API name of a group that includes only credentialed LWR site visitors</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e252 ">Queue</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e255 ">
              <ul>
                <li>The API name of a queue that includes only internal users</li>

                <li>The API name of a queue that includes only credentialed Aura site
                  visitors</li>

                <li>The API name of a queue that includes only credentialed LWR site visitors</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e252 ">Resource</td>

            <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e255 ">
              <p>The API name of a resource that contains one of these items at run time:</p>
              <ul>
                <li>The username of an internal user</li>

                <li>The username of a credentialed Experience Cloud site visitor</li>

                <li>The API name of a group that includes only internal users</li>

                <li>The API name of a group that includes only credentialed Aura site
                  visitors</li>

                <li>The API name of a group that includes only credentialed LWR site visitors</li>

                <li>The API name of a queue that includes only internal users</li>

                <li>The API name of a queue that includes only credentialed Aura site
                  visitors</li>

                <li>The API name of a queue that includes only credentialed LWR site visitors</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

At run time, assigned users, groups, and queues receive emails, notifying them that they have assigned work items. If you don’t want to send email notifications to assignees, see [Disable All Email Notifications for Work Item Assignments](https://help.salesforce.com/s/articleView?id=platform.orchestrator_manage_disable_default_email_notifications.htm&release=264.0.0&type=5 "By default, an orchestration sends an email notification when an orchestration work item is assigned or reassigned to a user, group, or queue. Disable all work item notifications to stop sending emails to internal users and credentialed Experience Cloud site visitors.").

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d111619e381">Assignee Type</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d111619e384">Notification</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Assignee Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e381 ">Internal user</td>

            <td data-label="Notification" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e384 ">Personalized email notification with a link to the internal related record
              page</td>

          </tr>
          <tr class="">
            <td data-label="Assignee Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e381 ">Credentialed Experience Cloud site visitor</td>

            <td data-label="Notification" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e384 ">Personalized email notification with a link to the related record page of the
              oldest live Experience Cloud site that they're a member of </td>

          </tr>
          <tr class="">
            <td data-label="Assignee Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e381 ">Group or queue of internal users</td>

            <td data-label="Notification" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e384 ">General email notification with a link to the internal related record
              page</td>

          </tr>
          <tr class="">
            <td data-label="Assignee Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e381 ">Group or queue of credentialed Aura or LWR site visitors who are all members of
              the same site</td>

            <td data-label="Notification" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e384 ">General email notification with a link to the related record page of the live
              Experience Cloud site that they're all members of</td>

          </tr>
          <tr class="">
            <td data-label="Assignee Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e381 ">Group or queue of credentialed Aura or LWR site visitors who are all members of
              one or more common sites</td>

            <td data-label="Notification" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e384 ">General email notification with a link to the record page of the oldest live
              Experience Cloud site that they're all members of</td>

          </tr>
          <tr class="">
            <td data-label="Assignee Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e381 ">Group or queue of credentialed Aura or LWR site visitors who have no site in
              common</td>

            <td data-label="Notification" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e384 ">
              <p>General email notification with a link to the internal related record page
              </p>
              <p style="margin-bottom:0;">The link is invalid for Experience Cloud site visitors, because they don't have
                access to internal pages. They can use the Orchestration Work Item Object List
                page to view and access their assigned work items from an Experience Cloud site
                that they're a member of.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Assignee Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e381 ">Group or queue of internal users and credentialed Aura or LWR site
              visitors</td>

            <td data-label="Notification" class="slds-cell-wrap" style="vertical-align:top;" headers="d111619e384 ">
              <p>General email notification with a link to the internal related record page
              </p>
              <p style="margin-bottom:0;">The link is invalid for Experience Cloud site visitors, because they don't have
                access to internal pages. They can use the Orchestration Work Item Object List
                page to view and access their assigned work items from an Experience Cloud site
                that they're a member of.</p>
            </td>

          </tr>
        </tbody>
      </table>

Orchestrations send email notifications from the Automated Process User Email Address specified in Process Automation Settings. If you don't specify this setting, Salesforce looks for an organization-wide email address with a purpose of Default No-Reply Address. If that doesn't exist, Salesforce uses any verified organization-wide email address. If no organization-wide email address exists, Salesforce uses the email address of the user running the orchestration. If the orchestration is running in system context without a user, Salesforce doesn't send the email. See [Set Up an Org-Wide Email Address for Orchestrations](https://help.salesforce.com/s/articleView?id=platform.orchestrator_deploy_create_org_wide_email_address.htm&release=264.0.0&type=5 "To send emails from Flow Orchestration, create an org-wide email address.").

You can customize the work item email notification sent to the initial assignee. If an orchestration work item is reassigned, Salesforce uses the default notification. For more information on customizing notification emails, see [Customize Emails to Assignees](https://help.salesforce.com/s/articleView?id=platform.orchestrator_customize_email_notification.htm&release=264.0.0&type=5 "By default, each time an orchestration run creates an orchestration work item, assignees receive a notification. To change the email notification sent when an orchestration work item is created, customize the associated approval step.").

## Where to Complete the Step

The assignee or a person from the assigned group or queue completes the associated screen flow on a related record page. A link to this related record page is included in the email sent to the assigned person, group, or queue.

## Running Context of a Flow Called by an Interactive Step

An active screen flow called by an interactive step runs in the context of the person who’s completing it.

#### See Also

- [Evaluation Flows in Orchestrations](https://help.salesforce.com/s/articleView?id=platform.orchestrator_concepts_flows_evaluation_flows.htm&release=264.0.0&type=5 "When you need more than 3 requirements to control stage and step execution, use an evaluation flow. Select the Evaluation Flow tile in the New Flow window to create an evaluation flow.")
- [Running Context of an Orchestration](https://help.salesforce.com/s/articleView?id=platform.orchestrator_concepts_running_user.htm&release=264.0.0&type=5 "The running context determines the access that an orchestration has to Salesforce data and the context used by a paused orchestration to resume. By default, the running context of an orchestration is the Automated Process User in system context.")