---
schema_version: "1"
id: fee75e81fdd894679fc4bd8431752dcfe2141a5b2d4f2052b31ab0ea6c775b0e
title: Provide Dynamic Revenue Orchestrator Access
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_provide_user_access.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_provide_user_access.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 29925005171c2e8a72a5cfacd6f8691958e976915374ca355475bafb689db1a7
description: Assign the appropriate permission set to give users Dynamic Revenue Orchestrator access, and review the permissions included in a permission set.
products:
  - Revenue Cloud
release: "264"
---
# Provide Dynamic Revenue Orchestrator Access

Assign the appropriate permission set to give users Dynamic Revenue Orchestrator access, and review the permissions included in a permission set.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d159308e63">User Permissions
              Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d159308e63 ">To configure deep cloning for fulfillment workspaces:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d159308e63 ">DRO Admin</td>

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

Standard DRO permission sets bundle the user, object, and field-level permissions each role needs, so assigning one is usually enough. For cases outside those roles, create a custom permission set. You'll need to configure each access layer yourself: user permissions, object permissions, and field-level security. For the full set of available permissions, see [Permission Sets in Dynamic Revenue Orchestrator](https://help.salesforce.com/s/articleView?id=ind.dro_permission_sets_in_dynamic_revenue_orchestrator.htm&release=264.0.0&type=5 "Permission sets extend the user's functional access without changing their profiles and are the recommended way to manage permissions. Dynamic Revenue Orchestrator (DRO) provides standard permission sets for administering DRO, designing fulfillment, managing fulfillment at run time, and submitting transactions. Assign the permission set that matches each user's role.").

1. Prepare the user for DRO. Identify the user's responsibilities and required access and assign the Fulfillment User permission set license. For assignment steps, see [Manage Permission Set Assignments](https://help.salesforce.com/s/articleView?id=platform.perm_sets_manage_assignments.htm&type=5&language=en_US). See [Assign a Permission Set License to a User](https://help.salesforce.com/s/articleView?id=platform.users_permissionset_licenses_assign.htm&language=en_US&type=5).
2. Turn on DRO. See [Turn On Dynamic Revenue Orchestrator](https://help.salesforce.com/s/articleView?id=ind.dro_turn_on_dynamic_revenue_orchestrator.htm&release=264.0.0&type=5 "You must turn on Dynamic Revenue Orchestrator so that your org is prepared to use it for fulfillment.").
3. Match the user to a permission set. Check whether a standard DRO permission set provides the access the user requires.
    - If yes, select the set with the least required access and assign it.
    - If no, start from the closest standard set as a base. Create a custom permission set, add the missing DRO and supporting user permissions, object permissions, and field-level security, and then assign it.
4. Confirm access works as expected. Verify the user's functional and data access. For order users, confirm Create, Read, Edit, and Delete (CRUD) access to order records. For example, use an expression set to append text to cloned record names or assign a different value to a custom field.
5. To review the exact user permissions, object access, and field-level security that a specific permission set grants, view its overview page in Setup.
    1. From Setup, enter Permission Sets in the Quick Find box, and select **Permission Sets**.
    2. Select the permission set that you want to view, such as **DRO Admin User**.
    3. Click **View Summary** to see the permission set's enabled object, user, field, and custom permissions, and the permission set groups that include it.

#### See Also

- [Permission Sets in Dynamic Revenue Orchestrator](https://help.salesforce.com/s/articleView?id=ind.dro_permission_sets_in_dynamic_revenue_orchestrator.htm&release=264.0.0&type=5 "Permission sets extend the user's functional access without changing their profiles and are the recommended way to manage permissions. Dynamic Revenue Orchestrator (DRO) provides standard permission sets for administering DRO, designing fulfillment, managing fulfillment at run time, and submitting transactions. Assign the permission set that matches each user's role.")
- [Create Fulfillment Users for Order Orchestration](https://help.salesforce.com/s/articleView?id=ind.dro_add_a_fulfillment_user.htm&release=264.0.0&type=5 "During fulfillment, Dynamic Revenue Orchestrator (DRO) uses the permissions associated with the fulfillment user rather than those of the user who submits an order. You can specify a different user for certain orchestration tasks, but generally, the permissions default to the fulfillment user. Select the fulfillment user from the Dynamic Revenue Orchestrator Settings pane.")