---
schema_version: "1"
id: 47a1e25353182e7a2b660f6c70095e6e36efe7867f9797bd829dbec1609d5487
title: Payments Personas and Permissions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/payments_personas_perms.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.payments_personas_perms.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e7fcc6a2e1b1b8b6e9f222706d308355c3b0550ae47e64d7b440239867b5b97d
description: A typical Salesforce Payments implementation involves several task-based personas that require certain permissions to do their jobs.
products:
  - Salesforce Payments
  - Commerce
release: "264"
---
# Payments Personas and Permissions

A typical Salesforce Payments implementation involves several task-based personas that require certain permissions to do their jobs.

### 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;"><a href="https://help.salesforce.com/s/articleView?id=commerce.payments_editions.htm&amp;language=en_US" target="_blank">View supported editions</a>.</td></tr></tbody></table>

  
| Persona | Description | Permissions |
| --- | --- | --- |
| Salesforce Administrator | Performs Salesforce configuration tasks. For example, the Salesforce administrator creates and configures user accounts and enables digital experiences. | The Salesforce Administrator is a high-level administrator with access to the Setup page, and can peform tasks related to users, profiles, and object management. |
| Payments Administrator | Performs Payments administrative task, including merchant account and payment method set creation and management. Runs reports and monitors activity in the Payments Workspace. | We provide a **Payments Administrator** permission set with access to manage Payments features. You can clone and modify the permission set for your own implementation. |
| Authenticated Payer | An external user who is registered with your store and can view and purchase products, and, if enabled, can save their payment methods. | We provide an **Authenticated Payer** permissions set for external user accounts to manage saved payments information. You can clone and modify the permission set for your own implementation. |
| Guest Payer | An external user who can view and purchase products from your store but isn’t registered. | As part of configuring a store, a Commerce admin can set up guest browsing to shop at a store. |
| Commerce Developer | Delivers customer value by developing and implementing payment experiences. 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. |

To view the permissions in a permission set, from Setup, in the **Quick Find** box, enter Permission Sets. Click the set you want to view, and in the System section, click **System Permissions**. Here’s an example of the Payments Administrator permission set.

![Payments administrator permissions list](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-payments-264-0-0-production-enus/c04ba30f-6dde-4ea7-949b-4f77b22b9fcb/payments/images/payments_administrator_permissions.png)