> 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/human-access/connections-and-integrations/integration-guides/claude.md).

# Claude

Connect Claude to Cakewalk for Auto Provisioning on the Team plan, using Google or a login link Agent Cake reads from your connected inbox.

### :sparkles: Auto Provisioning

| **Authentication method** | `Sign in with Google` and `Username and password`.                                        |
| ------------------------- | ----------------------------------------------------------------------------------------- |
| **Required permissions**  | `Admin`, `Owner` or `Primary Owner`                                                       |
| **Required metadata**     | `Plan`. Only `Team` is supported. See details [here](#which-claude-plans-are-supported).  |
| **MFA**                   | Not applicable. Claude accounts have no password, so there is no MFA secret to enter.     |
| **Email verification**    | Required with `Username and password`. See details [here](#how-email-verification-works). |

{% hint style="info" %}
**Provisioning creates an invitation, not an active member.** The person appears in your company's Claude organization as a pending invitation until they accept it. Until then they cannot sign in, and Cakewalk reports the access as granted.
{% endhint %}

{% hint style="info" %}
**Everyone is invited on a standard Team seat.** The seat type is fixed. Map the role you want through the permission levels above, not through the seat.
{% endhint %}

<details>

<summary><strong>Which Claude plans are supported</strong></summary>

Auto Provisioning works on the `Team` plan only. Pick `Team` in the `Plan` step.

`Enterprise` appears in the same list and is marked as not supported. Choosing it saves a configuration that every provisioning job then rejects, so leave it unselected.

</details>

<details>

<summary><strong>How email verification works</strong></summary>

These steps apply when the `Sign-in method` is `Username and password`. Despite the label, Claude has no password. Signing in means entering the admin account's email address, after which Claude sends a message containing a secure sign in link. Agent Cake reads that link from your connected inbox and follows it, so no one has to sit and watch the login.

Connect the inbox before you configure Claude. Go to Settings → Account → *Auto Provisioning* and click **Connect Inbox**. Full steps are in [Email Verification](/docs/human-access/how-to-guides/auto-provisioning/how-it-works/email-verification.md).

Until an inbox is connected, `Username and password` is greyed out in the `Sign-in method` step. Admins see a link to connect one. Everyone else sees a note to ask a Cakewalk Admin.

Agent Cake signs in as the inbox account itself, so the connected inbox has to be the mailbox of a Claude member with the `Admin`, `Owner` or `Primary Owner` role. You do not enter a separate Claude email address.

{% hint style="info" %}
The sign in link is short lived and single use. If it has not arrived by the time the login needs it, the run fails and you can retry the request.
{% endhint %}

</details>

#### Learn more

* [Roles and permissions](https://support.claude.com/en/articles/9267276-roles-and-permissions)
* [Manage members on Team and Enterprise plans](https://support.claude.com/en/articles/13133750-manage-members-on-team-and-enterprise-plans)
* [What happens to a user's data when they are removed from a Team or Enterprise organization?](https://support.claude.com/en/articles/12053672-what-happens-to-a-user-s-data-when-they-are-removed-from-a-team-or-enterprise-organization)


---

# 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/human-access/connections-and-integrations/integration-guides/claude.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.