## How it works

A role combines a merchant or shop level with permissions for individual areas. A member's assigned access scope determines where those permissions apply.

## Implementation

Use built-in admin, view-only, developer, operator, IAM or customer-support roles when they fit. Create a custom role when narrower access is required, selecting Hidden, Read and the permitted edit/write levels per area. Review payment-data visibility and connector restrictions separately. Role level may be locked while it is assigned to members or pending invitations.

## In this area

- Levels
- Built-in roles
- Create a custom role
- Access levels
- Areas

## Controls and values

| Control | Values and related labels |
| --- | --- |
| **Merchant** | `All shops (merchant-wide)` |
| **Shop** | `Specific shops or projects` |
| **Merchant Admin** | `Shop Admin` |
| **Merchant View Only** | `Shop View Only` |
| **Merchant IAM Admin** | `Shop IAM Admin` |
| **Merchant Developer** | `Shop Developer` |
| **Merchant Operator** | `Shop Payments Operator` |
| **Customer Support** | `Shop Customer Support` |
| **Level** | `Shop` |
| **Payment data visibility** | `Payment methods`, `Payment processors` |

## Related guides

- [Analytics exclusions](/docs/dashboard/settings/analytics-exclusions/)