You are here:
Commerce Personas and Permissions
A typical B2B implementation involves several task-based personas, such as commerce administrator, merchandiser, developer, and shopper.
Required Editions
| View supported editions. |
Which Salesforce Commerce Product Do I Have?
| Persona | Description | Permissions |
|---|---|---|
| System administrator | Performs Salesforce configuration tasks. For example, the system administrator creates and configures user accounts and enables digital experiences. | The system administrator is a high-level Salesforce admin with access to setup functionality, including tasks related to users, profiles, and object management. |
| Commerce administrator | Performs D2C Commerce administration tasks, including site configurations and permissions. For example, the commerce administrator creates stores and assigns members to stores. | We provide a Commerce Admin permission set, which you can pair with the Identity user license. You can also clone and modify the permission set for your own implementation. |
| Merchandiser | Designs and manages the storefront. Executes and maintains the best way to display and sell products. For example, the merchandiser imports products and configures search. | We provide a Merchandiser permission set, which you can pair with the Identity user license. You can also clone and modify the permission set for your own implementation. |
| Order Management administrator | Performs Order Management tasks. For example, servicing returns. | Use a permission set that has the Salesforce Order Management permission license and permission to the Order Management console app. Pair the permission set with the Identity user license. |
| Inventory manager | Configures and manages inventory functions using Omnichannel Inventory. | We provide an Omnichannel Inventory Manager permission set, which you can pair with the Identity user license. You can also clone and modify the permission set for your own implementation. |
| Developer | Customizes the storefront and implements advanced features. Builds and develops the commerce experience and apps. For example, the developer uses APIs to integrate a third-party application or uses code to develop a custom component. | The permissions required depend on the tasks that the developer performs for your implementation. |
| Buyer manager | (B2B stores only) Manages multiple buyers within a buyer account and multiple buyer accounts. | We provide a buyer manager permission set for external user accounts. You can also clone and modify the permission set for your own implementation. |
| Buyer | (B2B stores only) Purchases products or services for organizations to use or resell. An external user who is registered on your storefront and can view and purchase products. | We provide a buyer permission set for external user accounts. Pair the permission set with Customer Community and External Apps licenses to give users the minimum access to use B2B features. You can also clone and modify the permission set for your own implementation. |
| Shopper | (D2C stores only) An external user who is registered on your storefront and can view and purchase products. | We provide a shopper permission set for external user accounts. You can also clone and modify the permission set for your own implementation. |
| Guest customer | An external user who can view and purchase products from your storefront but isn’t registered. | As part of configuring your store, you can set up guest access to enable guests to shop on your storefront. |
Did this article solve your issue?
Let us know so we can improve!
