Overview roles and permissions
The following role/permission structure is designed to offer a high level of granularity and segregation of key responsibilities and duties within varying team sizes. Please contact us if you'd like to hear more about roles and permissions at Palisade or if your permission requirements might require something more bespoke.
Owner
An owner has full control over all aspects of the system. They can perform all actions across users, vaults, wallets, devices, transactions, API credentials, counterparties, addresses, policies, approval groups, and organisation settings.
Example: The CEO of a company who needs full control over all aspects of the system, including creating and managing users, vaults, wallets, and approving high-level changes.
Admin
Similar to Owner, but with slightly fewer privileges. Can manage most aspects of the system, including users, vaults, wallets, devices, transactions, and settings.
Example: A member of the C-suite responsible for day-to-day business operations that has executive power, handling user accounts, configuring vaults and wallets, and managing security settings.
Proposer
Can create and manage vaults, wallets, and transactions. Has limited access to user management and cannot perform high-level administrative tasks.
Example: A finance team member who needs to create transactions and manage vaults and wallets but requires approval for specific actions.
Approver
Primarily focused on approving transactions and some policy rules. Has view access to many areas but limited creation or modification rights.
Example: A senior finance officer responsible for reviewing and approving transactions, address book entries, and policy rules proposed by others.
Viewer
Has the most restricted access. Can view vaults, wallets, and transactions, but cannot create, modify, or approve most items.
Example: A junior team member or finance admin who needs to view transactions and basic information but doesn't have permission to make changes or approvals.
Auditor
Designed for oversight. Can view most aspects of the system, including users, vaults, wallets, devices, and transactions, but cannot make changes. Has access to view organization settings.
Example: An internal or external compliance or security officer who needs comprehensive view access to conduct audits and ensure regulatory compliance without the ability to make changes.
Updated about 2 months ago