To access Dynamic Revenue Orchestrator (DRO) features using a standard DRO permission set, users need the required permission set license and the appropriate DRO permission set for their role. This article explains how to assign both.
|
|
Important: Before you begin, make sure that you turn on Dynamic Revenue Orchestrator. |
All DRO permission sets require the Fulfillment User permission set license. See Assign a Permission Set License to a User.
|
|
Important: Without this permission set license, you can’t assign DRO permission sets or user permissions, and users can’t access DRO features. |
This table maps each role to its required permission set. Match each user's job responsibilities to a role in this table, and then review the permission set details in the Step3: Assign a DRO Permission Set section of this article to learn about the object, API, and UI access that each permission set grants.
|
Role |
Key Responsibilities |
Required Permission Set |
|---|---|---|
|
DRO Admin User |
A DRO admin user has unrestricted access to all DRO objects and is responsible for configuring DRO settings, enabling DRO features, and managing the overall configuration of the fulfillment framework. |
DRO Admin User |
|
Fulfillment Designer |
A fulfillment designer is a back-office user who designs and configures the end-to-end fulfillment framework for products and services. Fulfillment designers perform these tasks.
|
Fulfillment Designer |
|
Fulfillment Manager or Operator |
A fulfillment manager or operator is a back-office user who monitors and manages fulfillment at run time without configuring the framework. Fulfillment managers or operators perform these tasks.
|
Fulfillment Manager/Operator |
|
Submit Transactions and Fulfillment User |
A submit transactions and fulfillment user submits orders that trigger fulfillment processing. When this user submits an order, DRO performs order decomposition, plan composition, and plan execution, and creates the required fulfillment records. |
Submit Transactions and Fulfillment User |
|
Submit Transactions and Orchestrate User |
A submit transactions and orchestrate user submits orders processed through the DRO orchestration engine. |
Submit Transactions and Orchestrate User |
|
Submit Transactions User |
A submit transactions user submits transactions to DRO and calls the invocable actions. |
Submit Transactions User |
After you assign the Fulfillment User permission set license and determine the required permission set for your users based on their role, assign the required DRO permission set. Assigning a permission set provides both the corresponding workspace and object access. See Manage Permission Set Assignments.
The DRO Admin User permission set can be assigned only to users with the System Administrator profile. The other DRO permission sets can be assigned to any user with a standard Salesforce user profile.
|
|
Note: Assigning any of the standard DRO permission sets automatically grants the associated user permissions, object access, and field-level security. However, record visibility is governed by the sharing settings of your Salesforce org. Make sure that your organization-wide defaults and sharing rules allow users to see the records they need. See Set Up Record Access for Your Users. |
|
Permission Set |
Included User Permissions |
Considerations |
|---|---|---|
|
DRO Admin User |
Assigning the DRO Admin User permission set automatically assigns these user permissions.
See User Permissions. |
The DRO Admin User permission set is for users with the System Administrator profile. This permission set alone doesn't allow a user to submit an order. For users to submit orders, assign the Submit Transactions and Fulfillment User permission set as well. |
|
Fulfillment Designer |
Assigning the Fulfillment Designer permission set automatically assigns these user permissions.
See User Permissions. |
None |
|
Fulfillment Manager/Operator |
Assigning the Fulfillment Manager/Operator permission set automatically assigns these user permissions.
See User Permissions. |
The Fulfillment Manager/Operator permission set doesn't provide the broader configuration access granted by the Fulfillment Designer permission set. |
|
Submit Transactions and Fulfillment User |
Assigning the Submit Transactions and Fulfillment User permission set automatically assigns these underlying user permissions to users.
See User Permissions. |
None |
|
Submit Transactions and Orchestrate User |
Assigning the Submit Transactions and Orchestrate User permission set automatically assigns these user permissions.
See User Permissions. |
Unlike the Submit Transactions and Fulfillment User permission set, the Submit Transactions and Orchestrate User permission set doesn’t include product decomposition or enrichment capabilities, and is scoped to the orchestration engine only. Use it for non-sales transaction use cases, such as orchestrating quotes or custom objects, where product and order permissions are not required. |
|
Submit Transactions User |
Assigning the Submit Transactions User permission set automatically assigns the Submit Transactions User user permission. See User Permissions. |
The Submit Transactions User permission set allows users to submit transaction requests, but doesn’t provide access to any design or fulfillment tasks. |
This table lists the DRO object access automatically granted when you assign each standard DRO permission set. Assigning a permission set grants this access directly. There’s no additional configuration required.
|
|
Note: The Submit Transactions User permission set grants Read access to the User External Credential object, and no other access to any DRO objects. |
|
DRO Object |
DRO Admin User |
Fulfillment Designer |
Fulfillment Manager/ |
Submit Transactions and Fulfillment User |
Submit Transactions and Orchestrate User |
|---|---|---|---|---|---|
|
Asset Fulfillment Decomposition |
|
No access |
|
|
No access |
|
Fulfillment Asset |
|
|
|
|
|
|
Fulfillment Asset Attribute |
|
No access |
|
|
No access |
|
Fulfillment Asset Relationship |
|
No access |
|
|
No access |
|
Fulfillment Asset State Period |
|
|
|
|
|
|
Fulfillment Asset State Period Attribute |
|
No access |
No access |
|
No access |
|
Fulfillment Fallout Rule |
|
|
|
|
|
|
Fulfillment Line Attribute |
|
No access |
|
|
No access |
|
Fulfillment Line Source Rel |
|
No access |
|
|
No access |
|
Fulfillment Order |
|
No access |
|
|
No access |
|
Fulfillment Order Line Relationship |
|
No access |
|
|
No access |
|
Fulfillment Plan |
|
No access |
|
|
|
|
Fulfillment Scenario |
|
|
|
|
|
|
Fulfillment Step |
|
No access |
|
|
|
|
Fulfillment Step Definition |
|
|
|
|
|
|
Fulfillment Step Definition Group |
|
|
|
|
|
|
Fulfillment Step Dependency |
|
No access |
|
|
|
|
Fulfillment Step Dependency Definition |
|
|
|
|
|
|
Fulfillment Step Jeopardy Rule |
|
|
|
|
|
|
Fulfillment Step Source |
|
No access |
|
|
|
|
Fulfillment Task Assignment Rule |
No access |
No access |
No access |
No access |
No access |
|
Fulfillment Workspace |
|
|
|
No access |
|
|
Fulfillment Workspace Item |
|
|
|
No access |
|
|
Product Decomposition Enrichment Rule |
|
|
|
|
No access |
|
Product Decomposition Enrichment Variable Mapping |
|
|
|
|
No access |
|
Product Fulfillment Decomposition Rule |
|
|
|
|
No access |
|
Sales Transaction Fulfillment Request |
|
|
|
|
No access |
|
Value Transformation |
|
|
|
|
No access |
|
Value Transformation Group |
|
|
|
|
No access |
Assign a Permission Set License to a User
Manage Permission Set Assignments
Revenue Management Developer Guide: Dynamic Revenue Orchestrator Standard Objects
Dynamic Revenue Orchestrator Permissions
005459590

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.