Skip to main content
Delegated accounts (also known as delegates) start with no permissions and must be explicitly granted access. Permissions are granular, allowing vault owners to build precise guardrails by adding specific capabilities to each delegate.
  • Low-privileged delegates are ideal for performing routine tasks such as staking and farming.
  • High-privileged delegates can be used for more sensitive operations like trading and transfers.
This approach enhances security by ensuring that delegates can only perform intended actions within the defined boundaries:
  • It reduces the risk of unauthorized operations and accidental mistakes.
  • Even if a delegate is compromised, the impact is limited to the permissions granted to them.

​
Permissions

Permissions are protocol-specific capabilities defined by each integration program. They represent the smallest units of access that can be granted to delegates, allowing for fine-grained control over what actions each delegate can perform. Permission bitflags are stored as u64 integers, allowing for a maximum of 64 permissions per protocol. Follow the links in the table to view the permission definitions in program IDLs.

​
Pending Audit

This table lists permissions defined by integration programs that are pending audit.