---
schema_version: "1"
id: 4ba08fc75693867b12c0303dfccb0c0ba4a4e0b5516e8ab87f7862115ae4bef0
title: Fulfillment User
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/dro_fulfillment_user.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.dro_fulfillment_user.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 3ae74bdd2e64a38c7e11a5af18acacffad2fc56f26256e7f3340cf4f0fbe4825
description: A fulfillment user is the user whose permissions are used throughout the fulfillment process, unless you specify a different user at a more granular level. If you don't specifically configure a step to be run by a different user in the Run As User field, then Dynamic Revenue Orchestrator (DRO) uses the fulfillment user's permissions.
products:
  - Revenue Cloud
release: "264"
---
# Fulfillment User

A fulfillment user is the user whose permissions are used throughout the fulfillment process, unless you specify a different user at a more granular level. If you don't specifically configure a step to be run by a different user in the Run As User field, then Dynamic Revenue Orchestrator (DRO) uses the fulfillment user's permissions.

### 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>

Dynamic Revenue Orchestrator uses permissions and permission sets to determine whether a user can do certain things. When you set the fulfillment user, it's like telling DRO: from now on, pretend that this is the user that submits every order.

Make sure that the fulfillment user has at least the permissions granted by DRO Admin User or Submit Transaction User, and that it has the Assetize Order permission from the Revenue Lifecycle Management permission sets.

When you design a fulfillment step, you can enter a different user in the Run As User field. For example, design a callout that runs as a user who has permissions on the external system that you call out to. If you don't specify a user on a fulfillment step, then the step runs as the fulfillment user.

#### 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.")