Skip to main content
Governance gives workspace owners and admins one place to review projects, see what Genie AI has access to across the workspace, and enforce compliance rules that re-check every project automatically whenever it ships a new version.
Governance is part of every workspace by default — there’s nothing to turn on. A workspace that hasn’t written any compliance rules simply has nothing to check yet.

Open Governance

Click the account row at the bottom of the workspace sidebar, choose Workspace settings, then open Governance. Governance has these tabs: Projects, Integrations & Knowledge, Compliance rules and Spend. The workspace’s PII Detection, Guardrails, Activities and Tracing pages now live here too, as tabs of their own — see PII rules, Guardrails and Tracing.

Projects: review

The Projects tab lists every project in the workspace with its review status and compliance state. Open a project to set a verdict:
  • Approve — marks the project reviewed and compliant on its current version.
  • Flag — keeps the project running but records a note for other reviewers.
  • Disable — blocks new builds and prompts from everyone except the project’s owner. The owner sees your note, and once they publish a fixed version the verdict lifts automatically and the compliance rules re-run.
  • Clear verdict — removes the current verdict.
You can attach an internal note to any verdict. It’s visible to other reviewers, and — if you disable a project — to its owner.
Disabling a project immediately blocks builds for everyone but the owner. Reach for Flag instead if you just want to record a concern without interrupting work.

Integrations & Knowledge: shared-asset oversight

The Integrations & Knowledge tab is a read-only overview of everything shared workspace-wide that Genie AI can act with: every workspace-level MCP integration (server, auth type, and the tools it exposes) and every workspace-wide knowledge document. Use it to check what Genie AI has access to across all your projects at a glance.

Compliance rules

Turn your organization’s policies into automatic checks. Each rule is a plain-language failure condition — for example, “The project fails when it handles personal data without a visible lawful basis” — with a name, description, and severity (Low, Medium, High, or Critical).
1

Open Compliance rules

From the Governance page, open the Compliance rules tab and click New rule.
2

Start from a template or write your own

Genie ships with built-in templates you can start from: EU AI Act — prohibited practices, GDPR — personal data handling, No internal data in public projects, Every project has a description, No unresolved security issues, and Third-party services are declared. Or write your own failure condition from scratch.
3

Set a severity

Choose Low, Medium, High, or Critical to reflect how serious a failure is.
4

Save

Tick Check existing projects now to run the new rule against every current project immediately, or leave it unchecked and it applies the next time each project ships.
Genie checks each project against every enabled rule by looking at its name, description, visibility, connected integrations, and what its most recently published version actually shipped — never the contents of your chat conversations. Checks run automatically every time a project publishes a new version, and you can also trigger them manually: Run checks on a single project, Run checks on all projects from the project list, or Run on all projects from a specific rule. A rule’s own page shows analytics — how many times it’s run, how often it’s failed, and its results across projects over time.

Spend limits

The Spend tab shows what Genie AI’s model calls cost in this workspace — totals, the daily ceiling, recent runs and alerts. Every model call is checked against a hard limit before it runs: each run has its own budget, and rolling 24-hour ceilings cap what a person, the workspace and the whole platform can spend. A call that would cross a limit doesn’t run, and what a run had done up to then is kept. When a limit stops something — a chat turn, an agent run, Auto — it says which one, in plain words.
  • Open a run to see every call it made, with times, alerts and how it ended. A figure the provider didn’t report is marked estimated.
  • Anyone who may see Governance sees the workspace’s totals and runs. Members with Governance’s manage permission also see who started each run and a per-member breakdown, and may stop anyone’s run. Anyone can stop a run they started.
  • Ask Genie AI — “How much did our agents spend this week?” — and it reads the same data.
Platform-wide figures aren’t shown here, only the workspace’s own.

Who can access Governance

Owners and admins always have full access. Anyone else needs the See Governance permission, granted on a custom role (or on the built-in Member role, workspace-wide) from the Roles page — the same way you’d grant any other role permission. It’s a view-only grant: reviews and rule results, not rules or settings. Everyone else can’t open Governance.
Governance access used to be a separate per-member toggle on the settings page. That toggle is gone — if you’d granted someone view access that way before, grant it again as a role.
Owners and admins can also choose to hide private projects from the Governance view, from the workspace settings page.

Manage Governance from workspace chat

Ask the Genie workspace AI in plain language:
  • “Which projects are failing compliance right now?”
  • “Flag the customer-portal project — it’s handling PII without a policy”
  • “Create a compliance rule that every project must have a description”
  • “Run compliance checks on all projects”
Every Governance page has an Ask Genie AI button with a ready-made prompt for that page — including describing a policy in plain language and letting Genie draft the failure condition for you.

Guardrails

Control what Genie AI will discuss in your workspace.

PII rules

Detect and block sensitive data in chat.

Genie MCP Server

Manage governance programmatically from any MCP client.

Members and roles

Grant view access to Governance for a non-admin member.