> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/ai-agent-access/concepts/connection-and-agent-statuses.md).

# Connection and Agent Statuses

Connections and Agents each have their own status taxonomy. This page defines every status and what it means.

Cakewalk Agent Access tracks two parallel status taxonomies. Connection statuses describe the health of a User's credential for a downstream app. Agent statuses describe an Agent's wiring to the MCP Gateway and recent activity.

***

### 📖 Key Concepts

* **Connection status**: The health of one User's credential for one downstream app, and whether their org still allows them to use it.
* **Agent status**: The lifecycle state of an Agent in the org. Derived from session activity.

:bulb: *Why this matters:* Connection statuses tell you whether a User's credential for an app is usable. Agent statuses tell you whether an AI client is wired up and active. The two are independent. An Agent can be Active even if one of its Connections is in Error.

***

### 🔗 Connection Statuses

A Connection has one of five statuses.

| Status            | Meaning                                                                                                                                      |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| **Active**        | Authenticated and ready to use. Credential is in the vault.                                                                                  |
| **Error**         | Token expired or sync failed. Reconnect to restore.                                                                                          |
| **Paused**        | The User deliberately paused this Connection. Credential preserved; Agent access blocked until resumed.                                      |
| **Restricted**    | The User's groups are no longer allowed this Agent Connection. Credential preserved; Agent access blocked. Only an Admin change restores it. |
| **Not Connected** | The User has not authenticated to this app yet.                                                                                              |

```mermaid
%%{init: {"flowchart":{"nodeSpacing":80,"rankSpacing":60,"curve":"linear"}}}%%
flowchart TD
    N(["Not Connected"]) -->|"the User authenticates"| A(["Active"])
    A -->|"token expired<br/>or sync failed"| E(["Error"])
    E -->|"reconnect"| A
    A -->|"the User pauses"| P(["Paused"])
    P -->|"the User resumes"| A
    A -->|"the Connection leaves<br/>the User's groups"| R(["Restricted"])
    R -->|"the Connection returns<br/>to one of their groups"| A
```

#### Paused and Restricted

The two look alike and behave differently. Paused is something the User did and can undo. Restricted is the outcome of your org's [Connection access](/docs/ai-agent-access/how-to-guides/connection-access.md) setting, and only a change to what the User's groups are allowed lifts it.

A Restricted Connection keeps its card in My Connections, under the **Paused** tab, with a Restricted chip that explains why. The User can open its details but cannot resume it or connect it. Neither state costs a fresh sign in when it clears.

***

### 🤖 Agent Statuses

An Agent has one of three statuses.

| Status            | Meaning                                                    |
| ----------------- | ---------------------------------------------------------- |
| **Active**        | Agent is wired to the MCP Gateway and has recent sessions. |
| **Inactive**      | No sessions in the last 30 days.                           |
| **Not Connected** | Pre-registered or never connected. No sessions yet.        |

```mermaid
%%{init: {"flowchart":{"nodeSpacing":80,"rankSpacing":60,"curve":"linear"}}}%%
flowchart TD
    N(["Not Connected<br/>pre-registered, no sessions yet"]) -->|"a User sets it up through<br/>the MCP Gateway"| A(["Active"])
    A -->|"no sessions in<br/>the last 30 days"| I(["Inactive"])
    I -->|"new session"| A
```

***

### Related Concepts

* [The Three Actors](/docs/ai-agent-access/concepts/the-three-actors.md): Connections and Agents in the User-Agent-Connection model
* [Roles and Permissions](/docs/ai-agent-access/concepts/roles-and-permissions.md): what Admins and Members can do
* [Connection Access](/docs/ai-agent-access/how-to-guides/connection-access.md): the setting that produces the Restricted status


---

# 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://www.cakewalk.security/docs/ai-agent-access/concepts/connection-and-agent-statuses.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.