Roles and permissions: overview

There are 6 user roles currently available on the Palisade platform.

Please contact us for more information on these roles or if your organization requires a more bespoke role structure.

Owner

An owner has full control over all aspects of the system. They can perform all actions across all 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 that has executive power and is responsible for day-to-day business operations, including 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, such as finalising/sending transactions.

Approver

Primarily focused on approving transactions and some policy rules. Can view many areas of the platform but has 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.