Skip to main content
Dreamforce is streaming for free on Salesforce+. Watch now.

Configure Access and Permissions, and Payments

Learning Objectives

After completing this unit, you’ll be able to:

  • Describe the permission sets required to use Order Management.
  • List the permission sets that come with Order Management.
  • Explain how you can organize permission sets.
  • Explain why you need to configure field-level security.
  • Describe two ways to implement payment processing with Order Management.

Configure Your Org

Maria continues to configure her org for Order Management for users and permissions via these settings.

  • User access and permissions
  • Access to the console app
  • Field-level security
  • Custom field permissions

Users and Permission Sets

Maria reviews Order Management personas and permission sets to better understand which ones to assign to users. To access Order Management features, users must be assigned to one of two profiles.

  • System administrator
  • Standard platform user, including the Salesforce Order Management feature permission set license

Users must also have access to the Order Management console app and any customizations.

Permission Sets

Order Management comes with persona-based permission sets that include the Order Management permission set license. Here’s how Maria reviews them.

  1. Go to Setup.
  2. In the Quick Find box, enter Permission Sets and select Permission Sets.

Along with other permissions, she sees these.

Permission Set

Description

Order Management Operations Manager

Ability to manage day-to-day Order Management processes. 

Limited ability to modify open fulfillment orders.

Order Management Agent

Standard Order Management user.

Can only modify an open fulfillment order by advancing its status through the workflow.

Order Management Shopper

Limited access for a service user to allow an external system like a Salesforce B2C Commerce storefront to make self-service requests.

Read-only access to fulfillment orders.

Maria can’t modify the standard permission sets. But here’s what she can do.

  • Use these permission sets as is. She must also create at least one custom permission set to provide access to the console app and any customizations.
  • Clone and customize permission sets. Cloned permission sets count against her org’s limits.
  • Create one or more custom permission sets that include the license.

Maria can organize her permission sets in a few different ways.

  • Two or more (recommended): Use one or more permission sets for the Order Management permission set license and persona-based permissions.
    • Use the included permission sets or create custom permission sets with the Order Management permission set license.
    • Assign one Order Management permission set and the custom permission set to each Order Management user.
  • Multiple:  Use multiple Order Management permission sets.
    • Clone the included permission sets or create custom permission sets with the Order Management permission set license.
    • Add the console app permission and all custom permissions to each set.
    • Assign one of the sets to each Order Management user.
  • Single: Use a single permission set for all Order Management users.
    • Clone one of the included permission sets or create a custom permission set with the Order Management permission set license.
    • Add the console app permission and all custom permissions to the set.
Note

Important: If you assign more than one permission set with the Order Management permission set license to a single user, that user consumes multiple Order Management licenses.

Data Protection and Privacy

Data protection and privacy regulations can require you to mask or delete customers’ personal data. However, many fields on Order Management objects that contain personal data are read-only during normal processing. Only users with the System Administrator profile or the Edit Activated Orders permission can modify them. When designing data protection and privacy policies, make sure you account for this restriction.

Configure Access to the Console App

Next, Maria provides access to the console app for a permission set. Here’s how she does it.

  1. From Setup, in the Quick Find box, enter Permission Sets, then select Permission Sets.
  2. Click New to create a new permission set. (To add permissions to an existing set, select it.)
    • Enter a unique label: OM Console
    • To provide the Order Management license with this permission set, select it in the License dropdown list. Otherwise, leave --None-- selected.
    • Click Save.
  1. In the Apps section, click Assigned Apps.
    • Click Edit.
    • In the Available Apps box, select Order Management (standard__OMConsole), and click Add.
      Configure permissions for Order Management.
    • Click Save.
  1. Configure the permission set to access Account records.
    • Click the Permission Set Overview link.
    • In the Apps section, click Object Settings.
    • Select Accounts.
    • Click Edit.
    • If you use person accounts to represent shoppers, in the Account: Record Type Assignments section, select all the record types.
      Configure the permission set to access Account records.
    • If your org restricts sharing for Account records, in the Object Permissions section, select the View All checkbox.
  1. To check if sharing is restricted for Account records, from Setup, in the Quick Find box, enter Sharing Settings, then select Sharing Settings.
  2. Save the changes.

Repeat this process for each permission set for which you want to provide console app access.

Configure Field-Level Security

Maria wants to give the system administrator profile permissions to access specific fields on order-related objects. This lets admin users access Order Management functionality. Here’s how she does it.

  1. If you use person accounts to represent individual shoppers, verify that they’re enabled and configured in your org.
  2. From Setup, in the Quick Find box, enter Profiles, then select Profiles.
  3. In the list of profiles, select System Administrator.
  4. Scroll to the Field-Level Security section. For each order-related object, set Read and Edit access by object.
  5. Click View.
    • Click Edit.
    • For each field in the Read Access column of the table, select Read Access.
    • For each field in the Edit Access column of the table, select Edit Access.
      For each order-related object, set Read and Edit access by object.
  1. Click Back to Profile.

See the Salesforce Order Management Implementation Guide for detailed settings.

Configure Custom Field Permissions

Maria wants to add a custom field to an object to use in Order Management, and needs to allow Order Management users to access that field. Here’s how she gives access.

  1. From Setup, in the Quick Find box, enter Permission Sets, then select Permission Sets.
  2. Select the permission set that controls access for your Order Management users.
  3. In the Apps section, click Object Settings.
    • Select the object that has the custom field.
    • Click Edit.
  1. In the Field Permissions section, select the Edit Access checkbox for the custom field.
  2. Click Save.

To provide access to custom fields in multiple permission sets, repeat this process for each of them.

Configure Payments Processing

Processing payments is an important part of order management. To enable Order Management to execute payment captures and issue refunds, Maria integrates a payments component so she can view payment activity in the order payment summary for each order.

Payment processing means checking payment methods and issuing refunds via a third-party payment provider.

Salesforce Payments

For easy payment integration with Order Management, Maria installs the Salesforce Payments package, available on AppExchange.

Manually Configure a Payment Gateway

With Salesforce Payments, Maria can also add a payment gateway that a developer would configure manually, such as with Stripe or PayPal. This would enable her to view and manage payments in Order Management. Once the gateway is configured, she can link payments accounts and the Stripe and PayPal payments providers. These are the general steps a developer would take.

  1. Create a payment gateway adapter class using the Salesforce Apex connector framework. To help you get started, see these reference classes:
    https://github.com/forcedotcom/Core-Payments-Reference-Gateway-Integration-Adapters.
  2. Create a payment gateway provider record that points to the adapter class that you created.
  3. In Setup, define a named credential that contains the gateway provider’s authentication and login information. The adapter class callout definition calls the named credential.
  4. Create a payment gateway record to link the payment gateway provider record and the named credential.

Next Steps

In this unit, you configured user and permission set access to Order Management, access to the console app, field-level security, and custom field permissions. You also learned about payments processing. Next, learn how to use flows to define Order Management processing.

Resources

在 Salesforce 帮助中分享 Trailhead 反馈

我们很想听听您使用 Trailhead 的经验——您现在可以随时从 Salesforce 帮助网站访问新的反馈表单。

了解更多 继续分享反馈