# Governance

_Your tracking plan standards in one place: custom fields, PII, audit rules and stakeholders_

> 💡 Governance is available on the Enterprise plan only. See [plans and pricing](https://www.avo.app/pricing).

> 🚧 Governance is in beta. Reach out at [support@avo.app](mailto:support@avo.app) to get access and provide feedback.

The Governance page is the home for your tracking plan standards — how teams define what good looks like and have Avo enforce it. You'll find it under **Tracking Plan > Governance** in the sidebar of your Avo workspace, covering four areas:

- **Custom Fields** – admin-defined metadata fields, beyond Avo's built-in fields, that can be attached to events and properties
- **PII Types** – an admin-defined taxonomy for classifying which properties carry personally identifiable information
- **Audit rules** – the [tracking plan audit](https://www.avo.app/docs/audit/rules.md) that checks the whole plan against your standards, from naming conventions to required custom fields
- **Stakeholders** – [stakeholder teams](https://www.avo.app/docs/data-design/avo-tracking-plan/stakeholder-domains.md) that document who owns and depends on your tracking plan items

Custom Fields and PII Types are managed directly on the page; Audit rules and Stakeholders link out to their own surfaces and have their own docs.

![The Governance page under Tracking Plan in the Avo sidebar, showing the Custom Fields and PII Types tabs](https://www.avo.app/docs/images/governance/governance-page.png)

## Who can manage governance

Only workspace members with the _Admin_ role can create, edit and archive custom fields and PII types. All other roles see the Governance page read-only — the actions are disabled with the tooltip "Only workspace admins can manage governance fields and PII types".

Setting custom field values and PII status on individual events and properties is regular tracking plan editing, available to _Editor_ and _Admin_ roles. See [Members and roles](https://www.avo.app/docs/workspace-management/members.md) for the full role overview.

## Governance changes are branch-reviewed

Custom field and PII type definitions, and the values set on items, live in the tracking plan model. That means changes to them are made on [branches](https://www.avo.app/docs/data-design/branches.md), show up in branch diffs, and go through the normal branch review and merge workflow — the same as any other tracking plan change.

## Learn more

- [Custom fields](https://www.avo.app/docs/data-design/avo-tracking-plan/governance/custom-fields.md): Attach structured metadata to events, variants and properties
- [Tagging PII](https://www.avo.app/docs/data-design/avo-tracking-plan/governance/tagging-pii.md): Classify which properties carry personally identifiable information
- [Audit rules and configuration](https://www.avo.app/docs/audit/rules.md): Enforce governance standards through the tracking plan audit
- [Stakeholders](https://www.avo.app/docs/data-design/avo-tracking-plan/stakeholder-domains.md): Document which teams own and depend on your tracking plan items