Team roles and permissions#
Invite the people who build, run and support your payments to your Yusr dashboard. Each team member has one role per business, and the role decides what they can see and do. The same rules are enforced by the dashboard and the API behind it, so hiding a button is never the only protection.
Roles#
| Role | Who it is for |
|---|---|
| Owner | The account holder. Everything, including transferring ownership. Each business has exactly one Owner. |
| Admin | Senior staff who run the account day to day: team, settings, settlement account, keys and verification. Everything except transferring ownership. |
| Developer | Engineers integrating Yusr: API keys, webhooks, request logs, test-mode simulation and cancelling pending transactions. No access to business settings, the settlement account or the team. |
| Support | Customer support and operations: find transactions, export reports, check webhook deliveries and resend events. Read-only otherwise. |
| Viewer | Read-only access to the dashboard, transactions, settlements and webhook endpoints, for example for finance or auditors. |
Permission matrix#
This table is generated from the same permission definitions the platform enforces.
| Permission | Owner | Admin | Developer | Support | Viewer |
|---|---|---|---|---|---|
View dashboard and reportsdashboard.view | Allowed | Allowed | Allowed | Allowed | Allowed |
View transactionstransactions.view | Allowed | Allowed | Allowed | Allowed | Allowed |
Export transactions and settlements as CSVtransactions.export | Allowed | Allowed | Allowed | Allowed | Not allowed |
Cancel pending transactionstransactions.cancel | Allowed | Allowed | Allowed | Not allowed | Not allowed |
Simulate payments in test modetransactions.simulate | Allowed | Allowed | Allowed | Not allowed | Not allowed |
View settlements and balancessettlements.view | Allowed | Allowed | Allowed | Allowed | Allowed |
View webhook endpoints and delivery logswebhooks.view | Allowed | Allowed | Allowed | Allowed | Allowed |
Create, edit and delete webhook endpointswebhooks.manage | Allowed | Allowed | Allowed | Not allowed | Not allowed |
Resend webhook eventsevents.resend | Allowed | Allowed | Allowed | Allowed | Not allowed |
View API keys (masked)keys.view | Allowed | Allowed | Allowed | Not allowed | Not allowed |
Create, roll and revoke API keyskeys.manage | Allowed | Allowed | Allowed | Not allowed | Not allowed |
View API request logslogs.view | Allowed | Allowed | Allowed | Not allowed | Not allowed |
View business settingssettings.view | Allowed | Allowed | Allowed | Allowed | Allowed |
Change business profile, branding and payment behavioursettings.manage | Allowed | Allowed | Not allowed | Not allowed | Not allowed |
Change the settlement bank accountsettlement_account.manage | Allowed | Allowed | Not allowed | Not allowed | Not allowed |
View team membersteam.view | Allowed | Allowed | Allowed | Allowed | Allowed |
Invite, remove and change roles of team membersteam.manage | Allowed | Allowed | Not allowed | Not allowed | Not allowed |
Submit business verification (KYC)kyc.manage | Allowed | Allowed | Not allowed | Not allowed | Not allowed |
View the account audit logaudit.view | Allowed | Allowed | Not allowed | Not allowed | Not allowed |
Transfer account ownershipownership.transfer | Allowed | Not allowed | Not allowed | Not allowed | Not allowed |
| Two-factor authenticationRequired to sign in | Required | Required | Optional | Optional | Optional |
Two-factor authentication#
Owners and Admins must sign in with two-factor authentication (six-digit codes from any authenticator app that supports TOTP). If they have not set it up yet, they are asked to do so at their next sign-in, and they cannot turn it off while they hold that role. For every other role, 2FA is optional but strongly recommended; each person can enable it under Settings → Security.
Recovery codes are shown once when 2FA is enabled. Store them safely: they are the way back in if a phone is lost.
Inviting your team#
- Go to Team in the dashboard (you need the
team.managepermission: Owner or Admin). - Choose Invite member, enter their email address and pick a role.
- They receive an email with a link to accept. New users set a password; people who already have a Yusr login simply join your business, and can switch between businesses from the dashboard.
Pending invitations can be cancelled from the same page. You can change a member's role or remove them at any time; removing someone ends their access to your business.
Transferring ownership#
Only the current Owner can transfer ownership, to an existing team member. After the transfer, the previous Owner becomes an Admin. The new Owner must use two-factor authentication.
Audit log#
Changes to keys, webhooks, settings, the settlement account and the team are recorded in the account audit log
with who made the change, when, from which IP address, and the values before and after. Owners and Admins can read
it in the dashboard (the audit.view permission).
API keys are not people#
Secret keys act for the business, not for a team member, and are not limited by roles. Treat them like a password to the whole account: keep them on your servers, give access only to the people and systems that need it, and roll a key when someone with access leaves. See Authentication.