> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Choose an identity for C1 MCP

> Decide whether an AI assistant connects to C1 MCP as a person or an agent connects as a service principal.

Pick the identity C1 MCP sees before you connect anything. A person's AI assistant connects as that person. An agent that runs unattended or serves a team connects as a service principal with its own identity.

## Compare user and service principal connections to C1 MCP

| | User connection | Service principal connection |
| :- | :- | :- |
| **Who acts** | The person signed in to the AI assistant | The agent, as its own identity |
| **Typical clients** | Claude Desktop, Claude Code, Cursor, ChatGPT, Copilot | Scheduled jobs, agent platforms, chat bots, custom services |
| **How it signs in** | The person authorizes the connection in a browser | The agent exchanges a credential or platform identity token for an access token, with no browser |
| **What it can do** | What the person can do | What the service principal's roles and entitlements allow |
| **Appears in the system log as** | The person | The service principal |
| **Managed in** | **AI** > **C1 Gateway** > **Connected clients**, and each user's **AI & API** > **AI connections** | **Identities** > **Service principals** |
| **Governed by** | AI client type policy, per-client overrides, tenant-wide and per-server kill switches, and the person's access | The service principal's roles, entitlements, credentials, and federation trusts, plus tenant-wide and per-server kill switches |
| **Ends when** | The person revokes the connection, or an admin disables the client | An admin revokes the credential or deletes the trust |

## When to connect as a user

Connect as a user when a person drives the conversation and the assistant acts for them. Each person authorizes their own connection, and C1 MCP shows them only what they can already see.

See [Connect to C1 MCP as a user](https://www.c1.ai/docs/product/admin/c1-mcp/connect-as-user.md).

## When to connect as a service principal

Connect as a service principal when no person is present for each run, or when the agent's access must stay the same regardless of who built or operates it. Examples:

* A scheduled agent that posts an access digest every morning.
* A bot in a team chat that answers access questions for anyone in the channel.
* An agent built on a hosted agent platform that calls C1 MCP as a tool.

Avoid running these agents under a person's account. The agent would inherit that person's access, its actions would appear in the system log as that person, and it would stop working when that person's access changes.

See [Connect to C1 MCP as a service principal](https://www.c1.ai/docs/product/admin/c1-mcp/connect-as-service-principal.md).
