Organization accounts
An organization account lets a team share the same SVM workspace instead of operating from a single personal login. Members are invited by email and given one of two roles:
| Role | Access |
|---|---|
| Admin | Full access: invite and remove members, create transactions, change member roles, rename the organization — plus everything a reader can do. |
| Reader | Read-only access to the organization's vaults and data. |
Two separate sets of roles. Organization roles (admin / reader) govern access to the SVM workspace. They are not the same as the on-chain vault roles (DEFAULT_ADMIN_ROLE,MINT_ROLE, and so on) that gate actual vault transactions — those are managed per-vault on the Permissions tab. See Roles and permissions.
Upgrading a personal account
A new account starts as a personal (individual) account. To unlock team features, upgrade it to an organization from Settings → Organization.
This is irreversible. Upgrading converts your personal account into an organization. You can't convert it back.
to upgrade in the UI: open Settings → Organization, click Upgrade to Organization, enter an organization name, and confirm. You'll be logged out to complete the setup — log back in and select your organization to continue. The account that performs the upgrade becomes the first admin.
The organization name can be changed later by any admin.
Managing members
Only admins can manage membership. An invitation is sent to the member's email address; the role applies as soon as they accept. Removing a member revokes their access immediately — they can be re-invited later. You can't remove yourself.
in the UI: from Settings → Organization, use Add Member (enter an email, choose Admin or Reader), the edit icon on a row to change a role, or the remove icon to revoke access.
</>via the API:List:
listOrganizationMembers— returns each member'smemberId,name,role, andjoinedAt; available to any member.Invite:
inviteOrganizationMember— body{ email, role }.Change role:
updateMemberRole— body{ role }.Remove:
removeOrganizationMember.Rename the organization:
updateOrganizationName— body{ name }.All except listing require the admin role.
Extra verification. When the signed-in admin has MFA enabled, member management (invite, role change, removal) and renaming the organization each require a step-up two-factor confirmation before the action goes through.
Integrating via API
Members can drive the SVM programmatically with API keys, scoped to their own access. Keys are created and managed under Settings → API Keys; each key carries its own role and optional IP allowlist.
Related
- Roles and permissions: the on-chain vault roles, separate from organization membership
- The Staking Vault Manager: multi-user access and the rest of the SVM
- Subscribe to webhooks: wire vault and validator events into your own systems
Updated about 4 hours ago