> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/control-center/governance-operator.md). # Governance Operator The Governance Operator—ask about the account, and approve what it proposes. The Governance Operator is the chat surface in Control Center. Ask about platform activity, account usage, or a selected project. It coordinates the governance-review agents that hold the answer. You don't need to reconcile data across several screens. It differs from the Console Operator in one important way: **it doesn't act on its own.** It stages each proposed change for your approval. For general orchestration, see [Operator](/core-concepts/operator.md). This page covers Control Center behavior.

The Governance Operator chat, with suggested prompts (Summarise usage, App traffic, Token report) and a panel of system agents including Agent Performance Analyst and Billing & Credit Manager — The Governance Operator, with its operating team of governance-review agents.

## At a glance * **Where:** Control Center * **Scope:** **Account** activity, or one selected project. It covers usage, cost, access, guardrails, and change history. * **Acts:** never on its own. It **stages** an action and waits for you to approve it. * **Dispatches to:** an *operating team* of governance-review agents. This is the agent team described on [Operator](/core-concepts/operator.md). ## What it does **It answers cross-platform governance questions.** Ask what drove this month's cost, which agents were created recently, or which apps were published. The Operator routes each part to the relevant agent, then presents the combined result. **It orchestrates a team.** The Operator interprets your intent, breaks the request into tasks, and assigns each task to a suitable governance-review agent. Agents report their results to the Operator, which returns one response. **It stages, rather than acts.** It records the proposed fix. Nothing runs until you approve it. **It can narrow to one project.** Control Center screens are account-wide. The Operator has its own project selection, so you can investigate one project without changing the wider view. See [Accounts, Projects, Spaces](/start-here/how-qore-is-organized.md) for account and project scope. ### Related

Title	Description	Target
Operator	How an Operator coordinates a team of agents.	Operator
Console Operator	The Console Operator, and how it differs.	Console Operator
Agent Controls	Stop individual agents or all agent activity during an emergency.	Agent Controls
Control Center	The governance space where the Operator works.	Control Center

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.uptiq.ai/control-center/governance-operator.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.