Skip to main content

Introduction

Spending permissions set the asset, amount, renewal window, and destination a role can use.
  • Use when: a role should spend within a budget rather than have unrestricted access.
  • For: application signers, session keys, payment operators, and automated strategies.

How it works

  1. Choose the asset and amount in base units: lamports for SOL, mint base units for tokens.
  2. Choose a fixed budget or a recurring allowance measured in slots.
  3. Add a destination restriction when the role should pay only one recipient.
  4. Pair the limit with the program access needed for the operation.

SOL permissions

Token permissions

The token destination is the receiving token account, not its owner’s wallet address.

Staking permissions

SDK example

A recurring SOL allowance.
  • Grants up to 0.1 SOL per 1,000-slot window.
  • Pass actions to Add a role.
  • A fixed limit is a remaining budget, not a per-transaction maximum.
  • Recurring windows use slots, so they do not guarantee a calendar interval.
  • Opening a new session does not reset the role’s remaining spending budget.