> ## Documentation Index
> Fetch the complete documentation index at: https://docs.privy.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Assigning conditional policies

A key feature for organization wallets is the ability to configure **conditional policies**, where different users (or quorums of users) have different restrictions for the signatures and transactions they can execute with a wallet.

Conditional policies enable you to set up granular access control with organization wallets. Highly-sensitive or high value operations can be restricted to privileged individuals (the root key quorum) while day-to-day wallet operations can be provisioned to those with less permissions.

Follow the steps below to configure organization wallets with conditional policies.

<Steps>
  <Step title="Create additional key quorums">
    In addition to the root key quorum, create additional key quorums for members of the
    organization with lower privileges. In general, each key quorum should correspond to a specific
    set of permissions (e.g. the ability to transact \< 1000 USDC on Tempo).
  </Step>

  <Step title="Create policies for each key quorum">
    For each key quorum in the organization (including the root key quorum), define a policy for
    what actions that quorum should be able to take with the wallet (e.g. allowlisted addresses,
    transfer limits).
  </Step>

  <Step title="Attach the additional key quorums to the wallet as additional signers">
    Finally, when creating or updating the wallet, set the additional key quorums from step (1) as
    `additional_signers` on the wallet, with their `override_policy_ids` set to the ID for their
    corresponding policy. This provisions access to the wallet to that quorum of users within the
    scope of the associated policy.
  </Step>
</Steps>

View [this guide](/recipes/wallets/conditional-signer-policies) for a more in-depth walkthrough of conditional policies.