Your team
Account → Team is who can sign in to your PaySigna account and what each of them can do.
Inviting someone
Section titled “Inviting someone”Invite by email and assign a role. They set their own password; you never handle it. An invitation that is not accepted can be withdrawn.
Give people their own account. A shared login means your audit trail says “the account” did something rather than naming a person, which is useless the one time you need it — and it means a departure requires a password change for everyone.
Roles decide what the portal shows
Section titled “Roles decide what the portal shows”A role is a set of permissions, and nearly every page in the portal requires one. The sidebar hides what a user cannot reach rather than showing them a link that refuses them.
That is why two people on the same team see different portals, and it is deliberate: a menu full of items that answer “forbidden” teaches people to ignore refusals. If a colleague cannot find a section you can see, they are missing a permission.
Grant by job, not by seniority:
| They do | They need |
|---|---|
| Reconcile the books | Transactions, Balances, Settlements, Withdrawals — read |
| Handle customer problems | Transactions and Customers read, Refunds, Disputes |
| Run the integration | API keys, Webhooks |
| Administer the account | Team, Settings |
Two permissions deserve real thought before you hand them out:
- API keys. A key created here can move money from outside the portal, with no further login. This is the most powerful thing in the account.
- Settings → Settlement. Whoever can change the settlement destination can change where all of your money goes.
Neither belongs with “everyone who seems senior”. Keep both to a short list of people, and make sure that list is longer than one.
When someone leaves
Section titled “When someone leaves”Remove their access the same day. Then, if they held API keys, rotate those keys — removing a person does not invalidate a credential they copied, and a key they pasted into their own machine keeps working until it is rotated. See API keys.
Do not end up with one administrator
Section titled “Do not end up with one administrator”A single account holder is an outage waiting for a lost phone or an unexpected resignation. Have at least two people who can administer the account and change settings. This is the most common avoidable emergency we see.
The audit trail
Section titled “The audit trail”Privileged actions are recorded against the person who took them. That record is what makes a shared login genuinely costly, and it is the reason to give everybody their own account even when it feels like extra administration.
If you need to establish who changed something and when, ask [email protected].