# Merchant View admin roles

> What each role can do on the Merchant View Admin screens. Support and Support (read-only) can open them and export the wording, and change nothing.

What each role can do on the Merchant View Admin screens. Support and Support (read-only) can open them and export the wording, and change nothing.

### Everyone sees everything; the role decides the actions

Admin, Support and Support (read-only) all see the same screens and the same data. The role only decides which of the buttons below a user can use.

### Roles are the security, options are the layout

The role decides what a user can do. For an embedded session it is the `session.teams` value on the [deep link](/platforms/reference/operations/createdeeplink/), and a deep link can never give more than the session that created it holds.

[Merchant View options](/platforms/embedded-payments/activity-view-options/) (`features`, such as `refund`) only decide which buttons are shown. They never grant or remove a permission. To stop a user refunding, give them a role that cannot refund; hiding the button is not enough.

The full list by operation is in [Roles and permissions](/platforms/user-guides/rules-roles/).

### Who can use each button

| Screen | Button | Admin | Support | Support (read-only) | Rule |
|---|---|:---:|:---:|:---:|---|
| [Localisation editor](/platforms/user-guides/admin-localisation-edit/) | Import | ✓ | ✗ | ✗ | [Import branded strings from a file](/platforms/user-guides/rules-localisation-import-strings/) |
| [Localisation editor](/platforms/user-guides/admin-localisation-edit/) | Reset | ✓ | ✗ | ✗ | [Reset a branded string to its original](/platforms/user-guides/rules-localisation-reset-string/) |
| [Localisation editor](/platforms/user-guides/admin-localisation-edit/) | Save | ✓ | ✗ | ✗ | [Override a branded string](/platforms/user-guides/rules-localisation-update-string/) |