Appearance
Hub access and roles
The Partner API hub is the part of the Agio app where your team reads card data and manages API tokens and webhooks. Partner roles decide what each member of your partner organization sees and does there.
Roles apply to people who sign in to the Agio app. They do not apply to API tokens.
Access takes two steps. An organization admin adds the person to your organization. A super admin then gives them a partner role.
Roles
| Role | Access in the hub |
|---|---|
| Super admin | Everything below, plus API tokens, the treasury view, and role assignment |
| Card viewer | Card applications, cards, and card transactions |
| Compliance | Everything a card viewer sees, plus each cardholder's verification status |
| Integration | Webhook subscriptions |
A member can hold several roles and gets the access of all of them. A member with no partner role has no hub access, and the hub does not appear in their navigation.
Hub sections
| Section | Contents | Roles |
|---|---|---|
| Cards | Card applications with their cards, spending limits, and digital wallet results. Read-only | Super admin, Card viewer, Compliance |
| Transactions | Card transactions. Read-only | Super admin, Card viewer, Compliance |
| Tokens | Create, rotate, and revoke API tokens | Super admin |
| Webhooks | Add and remove subscriptions, rotate a signing secret, and resend a delivery | Super admin, Integration |
| Treasury | Treasury wallet address, USDC balance, per-wallet limits, and open negative card balances. Read-only | Super admin |
A cardholder's verification status appears in the Cards section for a super admin or a compliance member. A card viewer sees the rest of the cardholder's detail, with the verification status marked as not available.
A token created in the hub needs an expiry of at most 365 days. An organization holds at most 10 active tokens.
What the hub does not do
No partner role can move funds or change a card in the hub. These are API operations, signed with an API token:
| Task | Guide |
|---|---|
| Cancel, freeze, or replace a card | Manage cards |
| Fund a cardholder or withdraw to treasury | Fund and withdraw |
| Transfer between cardholders | Card-to-card transfers |
| Change a cardholder's identity or contact data | Onboarding |
An API token is not limited by partner roles. Every token of your organization can call every partner operation, including the ones that move collateral. In the hub, only a super admin can create, rotate, or revoke a token, so treat the super admin role as access to funds.
Who can move funds
| Where | Who |
|---|---|
| Partner API | Any API token of your organization |
| Agio app | A member with the Organization Admin or Trader organization role, or the partner super admin role |
| Partner API hub | Nobody. The hub has no action that moves funds |
In the Agio app, those three roles can send and swap from your organization's wallets. That includes the treasury wallet that funds your cardholders. A member whose only roles are Member, Card viewer, Compliance, or Integration cannot send from these wallets.
For someone who must see card data but never move funds, assign Member, Card viewer, and Compliance, and none of the three roles above.
Manage organization members
A person must be a member of your organization before they can hold a partner role. An organization admin manages members on the Organization page of the Agio app. For every other member these actions are switched off.
Organization admin is an organization role. It is separate from the partner super admin role, and one person can hold both. Both roles can move funds.
Invite a member
- Open the Organization page and choose the Members tab.
- Choose Add member. The invite button in the page header opens the same form.
- Enter the person's email, given name, and family name.
- Choose their organization roles. Member is the default. Add Organization Admin only for someone who should manage members and invites. Organization Admin and Trader also let the person send funds from your organization's wallets.
- Add an optional message, then choose Invite.
The person receives an email and joins when they accept it. Until then they appear as Invited on the Members tab.
Follow up on an invite
The Invites tab lists every invite, with filters for pending, accepted, cancelled, and expired. Open an invite to act on it:
| Action | When to use it |
|---|---|
| Resend | The person lost the email. Works until the invite expires or is accepted |
| Extend expiry | The person needs more time to accept |
| Delete | The invite went to the wrong person or is no longer needed |
Change, disable, or remove a member
Under All members on the Members tab, open the member's actions:
- Edit changes the member's organization roles. A member keeps at least one role.
- The Enabled switch in the same form turns a member's access off and on without removing them. A disabled member appears as Disabled.
- Remove member takes the person out of the organization after you confirm.
Disable or remove a member as soon as they leave your team. If they held the super admin role, also rotate or revoke any API token whose secret they could read.
Assign roles
A super admin assigns roles in the Agio app:
- Open the Organization page.
- Open the page menu and choose Partner roles.
- Choose a member, switch each role on or off, then save and confirm.
These rules apply:
- Only a super admin sees Partner roles.
- The person must already be a member of your organization. Invite them first. An invitation cannot carry a partner role.
- An organization keeps at least one super admin. The app refuses to remove the role from the only super admin, including from yourself.
When partner roles were introduced, organization admins became super admins and every other member became a card viewer. If nobody in your organization holds the super admin role, ask your Agio contact to assign it.
Common setups
| Person | Roles |
|---|---|
| Owner of the integration, its credentials, and the treasury | Super admin |
| Manager who reviews cardholders and their verification status | Card viewer and Compliance |
| Support agent who looks up cards and transactions | Card viewer |
| Developer who maintains webhook endpoints | Integration, optionally Card viewer |
Next: Provision a cardholder.