Overview#
What a Member can do in a Team is determined by their permissions. There are eight in total, split into wallet permissions and management permissions, and each can be granted individually.This page applies to Members only. The Team Creator holds all permissions, and Admin permissions are fixed at full scope; neither can be adjusted.The permissions#
| Permission | What it covers |
|---|
| View wallet addresses | Viewing wallet addresses |
| Initiate transactions | Initiating transactions and Web3 wallet connection requests |
| Approve transactions | Approving transactions and performing MPC signing |
| Permission | What it covers |
|---|
| Manage policies | Editing transfer policies, editing Approval Nodes (transaction and whitelist Approval Nodes), editing the whitelist approval flow |
| Manage members | Inviting members and changing member permissions |
| Manage API | Configuring API Keys |
| Manage whitelist | Editing the Address Whitelist |
| Manage wallets | Creating wallets, renaming wallets, changing wallet tokens, hiding and restoring wallets, viewing hidden wallet data, sending transactions from hidden wallets |
Granting and changing permissions#
A Member's permissions are set by the inviter when they join. Nothing is selected by default — grant only what the member needs.After a member joins, permissions can be adjusted in their member details. Changing member permissions is a key Team decision and takes effect only after Admins approve it under your Team's Decision Mode.What happens during a permission change#
After you save, the system runs an authorization process: it first verifies the cloud Trusted Execution Environment, then generates and verifies MPC key shards for that member. This takes about 20 seconds — keep the app in the foreground. If authorization fails, you can retry.This means a permission change is not a simple configuration write. Granting the approve-transactions permission is what gives that member the key shard needed to participate in signing; revoking it invalidates that shard.Things to note#
The approve-transactions permission bears directly on asset security. A member holding it participates in MPC signing and becomes part of what makes a Team transaction possible. Grant it only to members who genuinely need to carry that responsibility.When a member is removed from the Team, the shard they held is invalidated.Modified at 2026-08-26 02:51:05
