> 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/how-to-guides/users.md).

# Users

Users is the Admin's delegation map: every employee, the Agents acting on their behalf and the Connections those Agents access. Drill into any employee for their full delegation scope.

Users is the Admin's lens on Agent delegation across the org: who has Agents set up, what those Agents access and how active each employee is. Each row drills into a detail page.

***

### 📖 Key concepts

* **employee**: A person in the organization, synced from your HRIS or IdP or invited manually.
* **Delegation**: An employee allowing one or more Agents to act on their behalf via the MCP Gateway.
* **Delegation scope**: The total footprint of one employee's Agent activity: Agent count, Connections accessed, tool calls.
* **Sync vs manual**: When HRIS/IdP sync is on, the sync is authoritative and Users are read-only here. When sync is off, Admins manage Users by hand.
* **User Groups**: The groups that sync from your HRIS or IdP. They drive Policy conditions and, under Curated [Connection access](https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/connection-access.md), which Agent Connections each employee can use.

:bulb: *Why this matters*: Employee attributes (department, job title, team, location) already drive Policy conditions. The delegation map adds the second half: what each employee's Agents are doing.

***

### 📊 The Users table

* **Navigation**: Users.
* **What you see**: one row per employee.
  * While Connection access is set to Curated, a banner at the top counts the employees who are in no synced group. Those employees see no Connections at all, because every rule is written against a group. Select **View members** to see who they are, then assign them to a group in your HRIS or IdP. Cakewalk never writes group membership back, so the fix always happens at the source and arrives with the next sync.
  * **Name + email**, **Department**, **Role** and other HRIS attributes.
  * **Agents**: count of Agents acting on behalf of this employee.
  * **Connections**: icon stack of Connections accessed.
  * **Sessions (30d)**: Agent session count.
  * **Last active**.
* **Actions**: inviting, editing and removing Users requires HRIS/IdP sync to be off. When sync is on, your identity provider is the source of truth and these records are read-only here. When your company also runs Human Access, people are added and removed there and this view reads from the shared directory. See [how Human Access and Agent Access connect](https://www.cakewalk.security/docs/human-access-and-agent-access/how-human-access-and-agent-access-connect).
  * **Invite user**: creates a User record and sends the invite.
  * **Edit**: name, department, role, job title, team. These feed Policy conditions.
  * **Remove**: deletes the employee record.

***

### 🛠 User detail

**Navigation**: Users → click any row. The detail page opens on the Overview tab.

#### Overview

* **What you see**: identity and HRIS attributes (department, team, job title, tenure); an activity summary (sessions, Agent count, Connections count, last active); and a delegation scope summary, for example `This User has delegated to 3 Agents accessing 5 Connections with 284 tool calls in the last 30 days.`
* **Why it matters**: one line tells you whether this employee is a heavy delegator or a light user.

#### Connections

* **What you see**: every Connection this employee holds credentials for, with Connection status (Active / Error / Paused / Restricted / Not Connected), the Agents that use it, sessions (30d) and last active.
* **Actions** (per row or in bulk):
  * **Disconnect session**: ends the employee's active Agent sessions on that Connection immediately. The employee can start new sessions afterwards.
  * **Remove connection**: removes the employee's credentials and ends any active Agent sessions. The employee must reconnect to resume Agent access to the app.
* **Why it matters**: Disconnect stops what is running now. Remove also pulls the credential, so nothing new starts until the employee reconnects.

#### Sessions

* **What you see**: every session this employee delegated, across all Agents and Connections. The same nested pattern used elsewhere: Level 1 sessions, Level 2 tool calls, and a side panel with payloads and the Policies that fired.
* **Why it matters**: the investigation surface for one employee's activity.

***

### 📋 Users at a glance

| Surface         | Where                     | What you see / can do                                                                                      | Why it matters                              |
| --------------- | ------------------------- | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| **Users table** | Users                     | One row per employee: Agents, Connections, sessions, last active. Invite, edit and remove (sync off only). | The delegation map across the org.          |
| **Overview**    | Users → row               | Identity, HRIS attributes and the delegation scope summary.                                                | Heavy delegator or light user, in one line. |
| **Connections** | Users → row → Connections | Per-Connection status and activity for this employee. Disconnect sessions or remove connections.           | Per-credential view for one employee.       |
| **Sessions**    | Users → row → Sessions    | Every delegated session, drillable to tool calls and the Policies that fired.                              | Investigate one employee's activity.        |

***

### 🔗 Related pages

* [All Agents](https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/agents/all-agents.md)
* [All Connections](https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/connections/all-connections.md)
* [Agent Activity](https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/agents/agent-activity.md)
* [Policies](https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/policies.md)
* [Connection Access](https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/connection-access.md)
* [Org Settings](https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/org-settings.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.cakewalk.security/docs/ai-agent-access/how-to-guides/users.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
