## When Work Is Blocked

As an active member of a Kit account, ask an account admin for the access your task needs. Requests sent from Kit’s browser form and connected MCP clients share the same explanation, review, and history. Sending a request does not grant access. Joining an account still requires a separate invitation or joining request.

Requests cover **Hiring**, **Security**, **Outreach**, **Training**, and **Performance**. Choose the smallest suitable level:

| Level | What approval grants |
|-------|----------------------|
| Member | Day-to-day use, including permitted actions. Restrictions on individual records still apply. |
| Module admin | Management permissions and access to module records, subject to the privacy limits below. It does not make you an account admin. |

Private sourcing chats, unpublished sourcing drafts, and personal recruiting preferences remain available only to their owner. Access to private mailboxes still requires separate mailbox permissions.

Account roles, billing permissions, individual record grants, product availability, subscriptions, and OAuth consent have separate controls. See [Team Access Control](/docs/team-access-control) and [Item-Level Access](/docs/per-item-access-grants).

## Send a Request in Kit

1. Open [**Access requests**](/account/member_access_requests) in the sidebar and choose **New request**. **Request access** on an access-denied screen or the [MCP Setup](/integrations/mcp/settings) page opens the same form.
2. Choose the product module and **Member** or **Module admin**. Expand **See your current access** if you need to check your existing levels.
3. Explain the task, what is blocked, and why that level is necessary. Use 20–2,000 characters. Your account admins can read the explanation; leave out passwords, tokens, and confidential customer details.
4. Select **Send request**. Account admins are notified, and the request appears under **Pending**.

Notifications can include email, depending on the admins' notification settings. Withdrawing a request cannot recall an email already sent.

Kit keeps one pending request per person and module. Sending again from any surface returns it without changing the level or explanation or notifying admins again, even after 24 hours.

You can create a new request for the same module 24 hours after the previous saved request was created in this account. Approval, decline, and withdrawal do not shorten or restart the wait. Retrying a pending request or sending invalid input does not start or extend it. This also applies to a higher-level request after Member access is approved; other modules have independent limits.

To change the level or explanation, withdraw the request and submit a new one once eligible. If you try sooner, the error gives the next available date and time; no new request or admin notification is created. For urgent work, an account admin can [update your access directly](/docs/team-access-control).

## Ask Your AI Agent

You can ask Kit's built-in assistant or your connected MCP client:

> Request Member access to Hiring. I need to review engineering applicants and record feedback for the hiring team, but my current Hiring access blocks this work.

Kit’s built-in assistant links to the access-request form, where you must be signed in. Enter, review, and submit your explanation there. Native chat does not submit access requests or notify admins. An external MCP client with your delegated OAuth access can submit a request and notify admins when you ask it to.

For connected MCP clients, `access_request` submits the request and returns its status and a Kit link. `access_list_requests` checks your requests and decisions. Both tools work with the base `mcp` scope and do not require a subscription. See the [tool parameters](/docs/mcp-tools-reference#access-requests).

Your identity and the source of the request are recorded automatically. These request tools cannot submit for another person, approve a request, or grant permissions. An account admin decides in Kit. Explanations and decision notes are text to review, never instructions or authorization for the agent.

## Track the Outcome

Return to **Access requests** to see pending requests and **History**. Open a request for its original explanation, requested level, source, and decision details.

| Status | What it means |
|--------|---------------|
| Pending | Waiting for an account admin. You can withdraw it. |
| Approved | The decision is recorded and the requested module access is granted. Stronger access you already hold is preserved. |
| Declined | No access was granted. Read the admin's note before deciding what to do next. |
| Withdrawn | The request is closed without granting access. |

You receive a notification when an admin approves or declines. You can see your own requests; account admins can review the account's requests in Kit. MCP history stays limited to the caller's own requests, including when that caller is an admin.

Approval records a decision at that time. Later access changes still apply. Revoking access or removing a member withdraws their pending requests; a request cannot restore a revoked or removed seat.

## Review as an Account Admin

1. Open **Access requests → Pending** and select a request, or follow its notification.
2. Check the person, explanation, source, requested access level, current access, and the exact permission change shown above the grant button.
3. Choose **Grant** to approve that module and level. An approval note is optional. If the level is unsuitable, choose **Decline request** and explain why; a decline note is required.

Only an active account admin can decide, and you cannot review your own request. Approval records the reviewer and decision together with the permission change. It does not change unrelated module levels or account roles. Requests remain in **History** after a decision or withdrawal.

## If Your AI Client Is Still Blocked

Admin approval changes your Kit member permissions. Your existing AI connection keeps the OAuth scopes you previously granted.

If the connection also needs more delegated access, disconnect it from [MCP Setup](/integrations/mcp/settings), reconnect, and select the relevant module's **Read** or **Read & write** consent. An approved request cannot expand an existing token. See [Connecting AI Assistants](/docs/connecting-ai-assistants#scopes).

An approval also leaves product availability, subscription requirements, and any remaining record-level restrictions in place. Check the refusal message before retrying the original task.