Governance controls who can change your Ripple Custody environment, which approvals are required, and where those controls apply. It is built from four parts:
| Part | What it does |
|---|---|
| Domains | Define the organizational boundaries where users, accounts, policies, and other entities belong. |
| Users and roles | Define who can submit, approve, reject, or review governed actions. |
| Policies | Define the approval rules for each type of governed action. |
| Intents and approvals | Define the workflow that turns a proposed change into an approved and executed change. |
| Goal | Start here |
|---|---|
| Learn how governance works | Domains, Policies, and Intents and approvals |
| Design the model that should exist at launch | Design your genesis |
| Operate governance after launch | Manage domains, Manage users and roles, Manage policies, and Manage intents and approvals |
| Adapt working patterns | Domain examples, User and role examples, and Policy examples |
| Look up fields and valid values | Domain reference, Policy reference, and Intent reference |
Read the concept pages once to understand the model. Use the genesis pages when you are preparing the first environment state. Use the manage pages after the environment is running. Use examples only after you know which workflow you are trying to implement.
This structure keeps each topic in one place: concepts explain, genesis pages help you decide, manage pages tell you what to do, examples show patterns, and reference pages list fields and values.