Super Admin

The highest role. The person who completes the organization’s registration gets it automatically, and it is the only role that combines both halves of the business: setting the rules and moving the money.

Can / cannot

Can

Everything Admin can do: users, companies, settings, API credentials
Everything Treasury Manager can do: initiate, sign, and approve transactions
Change the approval policy rules
Manage the organization’s passkeys
Create their own passkey

Cannot

Skip the approval policy: their operations are evaluated too
Approve their own operations
Operate without having created their passkey
Approve other people’s passkeys, unless they are the root user

Being a Super Admin user does not make you the root user

You can have every permission in the product and still be unable to approve a teammate’s passkey: only the root user, who registered the organization, can do that.

When to use it

For the account owner and for whoever is responsible for it day to day. At the start, no one else.

When a specific request comes up, there is almost always a smaller role that covers it: “I need to approve payments” is Treasury Manager, “I need to invite people” is Admin. Promoting someone to Super Admin for one task also hands them everything else.

Next steps

Admin — the governance half of the role, without access to the money.
Treasury Manager — the money half, without access to the rules.
Root user — why having every permission does not let you approve a teammate’s passkey.
To make the account operational: no rules, no operations.