> 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/governance/controls-and-audit.md).

# Controls & Audit

Keep agents safe and accountable. Review **guardrail** results, use **agent controls** during emergencies, and inspect the **audit trail** for account changes.

{% columns %}
{% column %}

#### Protect agent activity

Review screened inputs and outputs. Stop an agent or all agents when immediate action is required.
{% endcolumn %}

{% column %}

#### Investigate changes

Trace configuration and access changes across the account.
{% endcolumn %}
{% endcolumns %}

#### At a glance

| Area               | Use it to                              | Start here                        |
| ------------------ | -------------------------------------- | --------------------------------- |
| **Guardrails**     | Review safety-rule evaluations         | [Guardrails](#guardrails)         |
| **Agent Controls** | Stop active agents during an emergency | [Agent Controls](#agent-controls) |
| **Audit Trails**   | Identify who changed what and when     | [Audit Trails](#audit-trails)     |

Use this area to answer three questions: what did guardrails catch, how do you stop an agent now, and who changed an account setting.

## Guardrails

Guardrails screens agent executions against safety rules and records the result. Open **Controls & Audit → Guardrails** to see recent evaluations.

<figure><img src="/files/hHNiGEObfcoK5Gc5FGIf" alt="The Guardrails screen, listing evaluations with agent, guardrail, type, and result columns"><figcaption><p>Guardrails, listing recent safety-rule evaluations.</p></figcaption></figure>

{% hint style="info" %}
This screen currently displays sample data — its title reads *Guardrails (Mock)*. Treat the figures and rows as illustrative until it's connected to live guardrail evaluations.
{% endhint %}

You can narrow by agent and search by agent or guardrail. The page summarizes recent activity: **Evaluations (24h)**, how many were **Blocked** and their share of traffic, the **Pass Rate**, and the number of **Active Rules**. Each row is one guardrail evaluation:

| Field         | What it shows                                                                                                                                              |
| ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Timestamp** | When the evaluation ran.                                                                                                                                   |
| **Agent**     | The agent whose input or output was screened.                                                                                                              |
| **Guardrail** | The rule applied — for example, **PII Filter**, **Toxicity**, **Topic Policy**, **Prompt Injection**, **Hallucination Guard**, or **Jailbreak Detection**. |
| **Type**      | Whether the guardrail ran on the **Input** (before the model) or the **Output** (after).                                                                   |
| **Result**    | **Passed** or **Blocked**.                                                                                                                                 |

## Agent Controls

Agent Controls shows the runtime state of every agent and gives you emergency kill switches. Open **Controls & Audit → Agent Controls**.

<figure><img src="/files/CtLbEjgFWdr6xYuUG3Ps" alt="The Agent Controls screen, with a Stop all agents button and a per-agent status list"><figcaption><p>Agent Controls, with emergency stop switches and per-agent runtime status.</p></figcaption></figure>

At the top, **Emergency controls** gives you a **Stop all agents** button. Below it, you can search for an agent and see its state:

| Field      | What it shows                                                   |
| ---------- | --------------------------------------------------------------- |
| **Agent**  | The agent's name.                                               |
| **Status** | Its runtime state — **Waiting**, **Completed**, or **Unknown**. |
| **Action** | A per-agent control to stop that agent.                         |

{% hint style="warning" %}
Stopping an agent aborts its in-flight threads immediately. You can start new runs again at any time, so the stop is not permanent — but work in progress when you stop it is lost. Use **Stop all agents** only in a genuine emergency.
{% endhint %}

## Audit Trails

Audit Trails is the account's change log — every configuration and access change, in one place. Open **Controls & Audit → Audit Trails**.

<figure><img src="/files/fe9QQrnhgZzz2JArjlZk" alt="The Audit Trails screen, listing changes with timestamp, actor, module, and action columns"><figcaption><p>Audit Trails, the account-wide change log.</p></figcaption></figure>

You can narrow by workspace, by actor, and by date range, and search by actor, module, or action. Entries are listed most-recent first:

| Field         | What it shows                                                                                            |
| ------------- | -------------------------------------------------------------------------------------------------------- |
| **Timestamp** | When the change happened.                                                                                |
| **Actor**     | Who made it (for example, `sagar@uptiq.ai`).                                                             |
| **Module**    | The area affected — for example, **Accounts**, **Marketplace**, **Users**, **Knowledge**, or **Agents**. |
| **Action**    | What happened — for example, **Created**, **Updated**, **User Invited**, or **Generated**.               |

## Related

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/807cab861e090edd0ce825909db3db1b28f73799" %}
[Control Center](/start-here/control-center.md)
{% endcontent-ref %}

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/9cd0c4d868b97b43a234c8d0ca5c3690fa58decb" %}
[Evaluation & Quality](/governance/evaluation-and-quality.md)
{% endcontent-ref %}

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/4d5234c8a07efab44ec5e24cc81c8c08bae3eafc" %}
[Logs & Data](/governance/logs-and-data.md)
{% endcontent-ref %}

{% content-ref url="/spaces/0qmgQjJ5aArDTj2ACFHG/pages/84115b130456683eaee9079209f1add7ef90110d" %}
[Account Settings](/governance/account-settings.md)
{% endcontent-ref %}


---

# 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/governance/controls-and-audit.md?ask=<question>&goal=<endgoal>
```

`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.