> Source: https://wexa.ai/docs/governance/overview

# Governance

Governance is how Wexa decides what a call may do, records what it did, and lets you inspect the record. Every call, on every surface, passes a policy decision, and a call can be held for a person to approve. Any project-scoped member can read approvals, lifecycles and the audit trail. Project admins decide approvals and change gates.

Start with `policy-and-approvals`, then follow a call by its `lifecycle_id`.

- [policy-and-approvals](/docs/governance/policy-and-approvals): Decide held calls, and set the write gate.
- [audit-and-lifecycle](/docs/governance/audit-and-lifecycle): Follow one call, and verify the audit trail.
- [field-sensitivity](/docs/governance/field-sensitivity): Choose who can see a connector's fields.
- [observability](/docs/governance/observability): Find where a slow or failing run went wrong.
- [governance](/docs/governance/governance): The REST routes for approvals, audit and policy.
- [request-approval](/docs/governance/request-approval): Ask a person to approve something your app does.
- [get-approval](/docs/governance/get-approval): Read an approval and its decision.