> 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/perk.md).

# Perk

Connect Perk for Auto Provisioning with Google or an emailed login code Agent Cake reads from your connected inbox.

### :sparkles: Auto Provisioning

| **Authentication method** | `Username and password` or [`Sign in with Google`](/docs/human-access/how-to-guides/auto-provisioning/how-it-works/sign-in-with-google.md). |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| **Required permissions**  | `Account admin`                                                                                                                             |
| **Required metadata**     | None                                                                                                                                        |
| **MFA**                   | Not applicable. Perk signs in with an emailed code, 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" %}
**Revoking access archives the person in Perk.** They lose access but stay listed under Archived, and their past trips remain. To give the same email access again later, unarchive them on the People page first. A pending invitation is revoked instead.
{% endhint %}

{% hint style="info" %}
**Accounts with more than one company:** Agent Cake adds new people to the Perk account's default company.
{% endhint %}

<details>

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

These steps apply when the `Sign-in method` is `Username and password`. Despite the label, Perk has no password here. Signing in means entering the admin account's email address, after which Perk sends a `Your Perk one-time password (OTP)` email from `login@perk.com` with an 8 digit code. Agent Cake reads that code from your connected inbox and enters it.

When Perk asks to confirm a new person, it sends a separate 6 digit verification code from `noreply@perk.com`. Agent Cake reads that one from the same inbox.

Connect the inbox before you configure Perk. 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).

Agent Cake signs in as the inbox account itself, so the connected inbox has to be the mailbox of a Perk member with the `Account admin` role. You do not enter a separate Perk email address.

{% hint style="info" %}
The login code is valid for 5 minutes. 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

* [Perk: Roles and permissions](https://support.perk.com/hc/en-us/articles/21926026235164-Roles-and-permissions)
* [Perk: Add new people to your account](https://support.perk.com/hc/en-us/articles/21925997364124-Add-new-people-to-your-account)
* [Perk: Archive and delete people](https://support.perk.com/hc/en-us/articles/21926016328860-Archive-and-delete-people)


---

# 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/perk.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.