Skip to main content
Try Cobo WaaS Skill in your AI coding assistant (Claude Code, Cursor, etc.). Describe your needs in natural language to auto-generate production-ready SDK code and debug faster ๐Ÿš€
In WaaS 2.0, permissions and wallet scopes are a crucial part of maintaining robust security and precise access control. They ensure that users, whether developers or end-users, are granted the appropriate level of access to resources and operations. This access control applies universally across all user categories:
  • General developers: API operations require specific permissions.
  • Cobo Portal Apps developers: Applications are restricted to accessing only the resources within their authorized scopes.
  • Cobo Portal users: Permissions control access to resources, operations, and transactions within Cobo Portal.
This permissions framework is designed to provide a seamless and secure user experience, aligning with organizational policies and compliance requirements.

โ€‹
Key concepts

โ€‹
Permissions

A permission is a specific combination of a resource and an operation, defining what actions a user can perform on a given resource. For example, transaction:withdraw indicates that the resource transaction paired with the operation withdraw grants permission to initiate withdrawal transactions. Permissions govern functional access, specifying which actions users are authorized to perform, while data boundaries are controlled through wallet scopes.

โ€‹
Wallet scopes

A wallet scope defines the boundaries within which wallet-related permissions are effective, specifying access at levels such as wallet type, wallet ID, and other identifiers. Each type of wallet scope limits permissions to a specific subset of resources, ensuring a tailored access model. The wallet scope dimensions include:
  • Wallet type
  • Wallet sub-type
  • Project ID (for MPC Wallets only)
  • Vault ID (for MPC Wallets only)
  • Wallet ID

โ€‹
User roles

A user role is a collection of permissions that defines what resources and actions are available to users. Each role grants a specific set of permissions that determine usersโ€™ capabilities, such as viewing, operating, or managing resources. For more information, refer to Introduction to user roles and permissions.

โ€‹
Assign and manage permissions

โ€‹
General developers via API key

For general developers, permissions and wallet scope are associated with the API key. When you register an API key, you select user roles and define the wallet scope, which grants shared permissions to all developers using that key. For more details, refer to API key and Register an API key.
Editing an API keyโ€™s roles or wallet scope in Cobo Portal requires Admin approval in Cobo Guard before the change takes effect. Until an Admin approves the pending request, the previous (narrower) permissions remain active. If you have updated permissions but still receive HTTP 403 / error code 2025 or 4001, check whether the Cobo Guard approval has been completed.

โ€‹
Cobo Portal Apps developers via Org Access Tokens

Permissions for Cobo Portal Apps to access usersโ€™ organization resources are granted through an Org Access Token. When a user installs an app, the necessary permissions and wallet scope are set, and once approved by the organizationโ€™s admin, these are linked to the appโ€™s Org Access Token. Therefore, before publishing an app, developers should specify both required and optional permissions in the appโ€™s manifest file to ensure proper access is granted. For a comprehensive list of permissions, refer to Permissions list.

โ€‹
Cobo Portal users via user roles

Permissions for Cobo Portal users are based on their user role and wallet scope, with predefined roles available and customizable options for specific needs. For more details, refer to Assign user roles to members.