Each Dynamic Revenue Orchestrator (DRO) permission set is composed of one or more user permissions, which are the individually assignable capabilities that control access to specific objects, invocable actions, and UI pages. Assigning a DRO permission set also enables several supporting permissions needed for that role to function. These aren't typically assigned separately, but are listed here for a complete picture.
The DRO user permissions are the primary permissions that the DRO permission sets are built around. Learn about each DRO user permissions so that you can assign users only the access that they need.
This table lists the DRO UI pages and invocable actions that each user permission grants access to.
|
DRO User Permission |
Included in Permission Set |
UI Access |
Invocable Action Access |
|---|---|---|---|
|
System Administrator access for DRO User |
DRO Admin User |
| |
|
Allows user to gain Fulfillment Designer level access to DRO |
Fulfillment Designer |
|
No access |
|
Allows user to gain Fulfillment Manager or Fulfillment Operator level access to DRO |
Fulfillment Manager/Operator |
|
No access |
|
Submit Transactions and Fulfillment User |
Submit Transactions and Fulfillment User |
| |
|
Submit Transactions and Orchestrate User |
Submit Transactions and Orchestrate User |
The Launch Flow and Execute Actions actions |
No access |
|
Submit Transactions User |
|
Condition Builder (submission context) and Asset Attribute View pages |
|
If you build a custom permission set using DRO user permissions instead of a standard DRO permission set, this table lists the object access you must separately configure to match standard permission set behavior. Assigning a user permission does not grant this access automatically. You still need to add the corresponding object permissions and field-level security yourself.
|
|
Note: The Submit Transactions User user permission grants Read access to the User External Credential object, and no other access to any DRO objects. |
|
DRO Object |
System Administrator access for DRO User |
Allows user to gain Fulfillment Designer level access to DRO |
Allows user to gain Fulfillment Manager or Fulfillment Operator level access to DRO |
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 |
|
Fulfillment Fallout Rule |
|
|
|
|
|
|
Fulfillment Line Attribute |
|
No access |
|
|
No access |
|
Fulfillment Line Source Rel |
|
No access |
|
|
No access |
|
Fulfillment Order |
|
No access |
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 |
|
|
|
|
|
|
Fulfillment Workspace Item |
|
|
|
|
|
|
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 |
|
|
Note: Most of the remaining permissions are Revenue Management, other product, or Salesforce platform permissions, and aren’t specific to DRO. They're included in DRO permission sets because DRO's design and fulfillment features depend on them. |
These Revenue Management user permissions are included in some of the DRO permission sets.
|
User Permission |
Purpose |
Included in Permission Set |
|---|---|---|
|
Activate Orders |
Change an order's status to Activated. This step is performed before fulfillment can begin. |
|
|
Edit Activated Orders |
Edit an order after it's been activated. |
|
|
Manage Product Catalog |
Create, read, edit, delete Product Catalog Management objects. |
|
|
Manage Product Discovery |
Configure Product Discovery settings. |
DRO Admin User |
|
View Product Catalog via API |
Read Product Catalog objects through API. |
|
|
View Product Catalog Objects |
Read Product Catalog objects on the UI. |
|
These other product or Salesforce platform user permissions are included in some of the DRO permission sets.
|
User Permission |
Purpose for DRO |
Included in Permission Set |
|---|---|---|
|
Context Service Admin user. |
Configure context definitions used by DRO's decomposition logic. |
DRO Admin User |
|
Context Service Run time user. |
Read Context Service data at run time. |
|
|
Grant users access to Industries Interaction Calculation features. |
Access Industries interaction and pricing calculations used by DRO. |
|
|
Manage Flow |
Create, edit, and activate flows used in DRO automation. |
|
|
Run Flows |
Run active flows launched from DRO records. |
|
|
Provides internal Org users with access to Decision Explainer features and APIs. |
View system-generated explanations of DRO decomposition decisions. |
|
|
Access Actionable Relationship Center |
Access Actionable Relationship Center features that some DRO implementations use. |
|
|
Customize Application |
General Salesforce Setup and configuration access, needed to configure the DRO app. |
DRO Admin User |
|
Manage Custom Permissions |
Create and edit custom permissions. |
DRO Admin User |
|
View Setup and Configuration |
Read-only view of setup pages. |
|
|
View Roles and Role Hierarchy |
View the role hierarchy. |
|
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
005459959

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.