> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://zuora.ferndocs.com/docs/platform/extensibility/workflow/create-and-manage-workflow-definitions/workflow-reference/multi-entity-in-workflow/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://zuora.ferndocs.com/_mcp/server. # Multi-entity in Workflow > Describes how Zuora Workflow supports the Multi-entity feature and how to specify the target entity when configuring Workflow tasks. Describes how Zuora Workflow supports the Multi-entity feature and how to specify the target entity when configuring Workflow tasks. When Multi-entity is enabled for your tenant, Workflow can run tasks to interact with any entity in your multi-entity hierarchy that the Workflow OAuth user has access to. Most tasks that interact with Zuora data include an **Entity** selector so you can choose which entity the task operates with. For an overview of Multi-entity, see [Overview of Multi-entity](/docs/platform/user-management/multi-entity/overview-of-multi-entity). ## Prerequisites Before you use Multi-entity in Workflow, ensure the following requirements are met: * Multi-entity is enabled for the tenant. Your Zuora tenant must have the Multi-entity feature enabled. If your tenant has only one entity, the **Entity** selector is not displayed in Workflow task settings. * Workflow OAuth user has access to multiple entities. Workflow uses the OAuth credentials configured in global Workflow settings to authenticate API calls. Configure the OAuth client ID and client secret on the Workflow Settings tab. For instructions, see [Configure OAuth login for Workflow](/docs/platform/extensibility/workflow/configure-global-settings-of-workflow/zuora-login-of-workflow). The user associated with the OAuth client configured in Workflow settings must have access to the entities you want Workflow to operate in. Entity administrators can grant a user access to additional entities in the hierarchy. For instructions, see [Grant user access to other entities](/docs/platform/user-management/multi-entity/multi-entity-user-management/user-access-within-multi-entity-hierarchy/grant-user-access-to-other-entities). > **Note** > > The Entity dropdown lists the entities available to the Workflow OAuth user. If an entity does not appear in the list, verify that the OAuth user and OAuth client have access to that entity. ## How entity selection works Workflow determines the target entity for a task using the following order of precedence: 1. Task-level Entity setting - The entity selected in the **Entity** dropdown on a supported task. 2. Workflow-level Entity setting - The entity configured in the workflow definition settings (Entity Selection on the workflow configuration page). 3. Default entity - If no entity is specified, Workflow uses the default entity for the tenant. > Describes how Zuora Workflow supports the Multi-entity feature and how to specify the target entity when configuring Workflow tasks. ## Docs - [Specify the entity for a task](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/create-and-manage-workflow-definitions/workflow-reference/multi-entity-in-workflow/specify-the-entity-for-a-task.md): Specify which entity a workflow task uses by selecting an entity, inheriting it from the workflow, or passing an entity ID at run time. - [Task types that support the Entity selector](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/create-and-manage-workflow-definitions/workflow-reference/multi-entity-in-workflow/task-types-that-support-the-entity-selector.md): Lists the task types that support the Entity selector on the task settings. - [Entity selection for Callout tasks](https://zuora.ferndocs.com/docs/platform/extensibility/workflow/create-and-manage-workflow-definitions/workflow-reference/multi-entity-in-workflow/entity-selection-for-callout-tasks.md): Notifications: Callout and Notifications: Asynchronous Callout use the task-level Entity dropdown on the Authentication tab.