# Administration — Governance

![Administration — Governance](/docs-content/e70811210c-04-governance.png.webp)

**Navigation:** Administration → Governance  
**Primary audience:** governance, privacy, security, legal, compliance, data, and authorized platform administrators

## Purpose

Governance configures and reviews eligibility, user acceptance, permitted purposes, jurisdictions, sensitive categories, retention, legal hold, external sharing, and controlled feature activation.

## Scope controls and indicators

Environment selects the governed environment. Control Family filters policy groups. Jurisdiction selects configured regions. Review State filters healthy, review due, incomplete, draft, or exception.

Active Policies shows effective controls. Acceptance Coverage shows eligible-user completion. Jurisdictions counts configured legal or policy regions. Reviews Due identifies controls requiring owner action.

## Governance control families

Cards summarize Eligibility & Acceptance, Permitted Purposes, Jurisdictions, Sensitive Categories, Retention & Legal Hold, and Feature Flags. Each shows current state, coverage, owner, review date, and exceptions.

## Jurisdiction coverage

The matrix shows whether configured activities—such as meeting analysis, internal meetings, compliance review, or external sharing—are permitted, restricted, or not configured by jurisdiction. Selecting a cell opens the applicable rule and affected workspace.

## Governance attention and assurance

Attention lists due retention reviews, unmapped sharing purposes, feature pilots, or other gaps. **Control assurance** summarizes completeness by family. **Policy changes pending** shows prepared changes and required approvals. **Governance actions** provides mapping, approval, and rollout decisions.

## Actions

- Open or prepare a governance-policy change.
- Map a purpose or jurisdiction.
- Review eligibility and acceptance coverage.
- Create or release a legal hold under authority.
- Configure retention or sensitive-category handling.
- Review, approve, suspend, or end a feature rollout.

## Recommended procedure

Start from purpose, eligible population, and jurisdiction. Review downstream impact before approving a policy or feature change. Require explicit authority for restricted processing and test rollback or suspension before Production activation.

## Related screens

[Organization](/documentation/packages/bnd-org/screens/administration-organization), [People & Access](/documentation/packages/bnd-org/screens/administration-people-and-access), [Ethics Policies](/documentation/packages/bnd-ethics/screens/intelligence-ethics-policies), and [Audit & Security](/documentation/packages/bnd-aiops/screens/administration-audit-and-security).