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

# Authorize a connection

> Sign in to Claimr from your AI assistant and choose which organizations, campaigns, and permissions the connection gets.

When your AI assistant connects to Claimr for the first time, it opens a Claimr sign-in page. You sign in, then choose exactly what the assistant can reach. Nothing is shared until you click **Authorize**.

## Sign in

Sign in with the email and password of your Claimr admin panel account, or click **Sign in with Google** if you use Google to sign in to the panel.

The page shows the name of the assistant asking for access, for example "Claude is requesting access to your Claimr account". If you don't recognize the assistant, close the page.

## Choose what the assistant can access

After you sign in, the consent screen has three sections.

<Steps>
  <Step title="Organizations">
    Choose **All organizations** or **Specific organizations**. The list only shows organizations you belong to that have MCP access turned on.
  </Step>

  <Step title="Campaigns">
    Choose **All campaigns** or **Specific campaigns**. With specific campaigns, pick them from the list, grouped by organization. The list only shows campaigns your role can open.
  </Step>

  <Step title="Permissions">
    Choose **Full access** or **Limited access**. With limited access, set **Read** and **Write** for each area in the table below. Turning on **Write** also turns on **Read**.
  </Step>
</Steps>

Click **Authorize** to finish. Your assistant receives access and you can go back to the chat.

<Tip>
  Start narrow. Give a new connection one campaign and only the areas you plan to work on. You can change this later from your profile.
</Tip>

## Permission areas

| Area | What it covers |
| - | - |
| **Campaigns** | Campaign settings, groups, images, and descriptions |
| **Quests** | Quests, tasks, and pre-quests |
| **Rewards** | Daily check-ins, forms, items, prize pools, raffles, teams, and tiers |
| **Tournaments** | Tournaments and raffles tied to them |
| **Customization** | Custom CSS, layout, widget options, and translations |
| **Segments** | User segments |
| **Organization** | Creating new campaigns |

**Read** lets the assistant look at an area. **Write** lets it create, change, and delete things in that area.

## Your role always applies

A connection can never do more than your own team role allows. If your role can't edit quests in a campaign, the assistant can't either, even with **Full access**. The consent screen only narrows what your role already permits. See [Team roles and management](/team-roles-and-management).

A request goes through only when all of these allow it:

1. Your role in the organization and campaign.
2. The organizations and campaigns you chose for the connection.
3. The permission areas you chose for the connection.
4. MCP access being turned on for the organization.

## How long a connection lasts

A connection stays signed in while you use it. Your assistant refreshes its access automatically in the background. A connection that goes unused for 90 days expires, and your assistant asks you to sign in again.

You can revoke a connection at any time. See [Manage connections](/mcp/manage-connections).

## If you see no organizations

If the consent screen doesn't list any organizations, you'll see one of these messages:

* **"You don't belong to any organization yet."** Ask an organization admin to invite you. Access appears automatically once you join.
* **"None of your organizations have MCP access yet."** Your organizations are still on the waitlist. Contact [support@claimr.io](mailto:support@claimr.io) to request access.