Skip to content

Ask for and resolve access requests

An access request turns a refusal into something an administrator can act on. When Elaichi blocks you, you ask for access from the place where you were blocked, so you do not have to find an administrator yourself.

Where to find it: Governance → Access requests

Before you start

Task Permission you need
File a request, see your own requests, or withdraw your own request None. Every member can.
See the whole organization's queue, and approve or deny requests Manage members (member:manage)

File a request

  1. Find the blocked item. In the console, a restricted connector or tool shows a restriction icon. In an AI client, the refusal appears as a card.
  2. Choose the icon in the console, or Ask an admin for access on the card in your AI client.
  3. Optionally, add a Note that says what you need it for. One line is enough.
  4. Choose Ask an admin.

You will know it worked when the request appears under Governance → Access requests with the status Pending.

A request records what you asked for and why Elaichi refused it: a missing permission, or an organization restriction. A request about a restriction never names the rule, its author or its scope.

Info

You can have one open request for each item. If you ask again for something you already asked for, Elaichi reopens your earlier request instead of adding a second one.

Review the queue

With member:manage, the Access requests tab shows every request in your organization.

Column What it shows
Requester Who asked.
Tool The tool or connector they asked for.
Reason Whether a missing permission or a restriction blocked them.
Note The requester's own words.
Status Pending, Approved, Denied or Withdrawn, and who decided.
Requested When the request was filed.

Search matches the tool and the note. The status filter narrows the list. Both run on the server, so they cover the whole queue and not only the rows on your screen.

Without member:manage, the tab shows only your own requests, with the same columns except Requester.

Approve or deny a request

  1. Open Governance → Access requests.
  2. Open a Pending request.
  3. Optionally, add a Note that explains your decision.
  4. Choose Approve or Deny.

Approving a request about a connector restriction lifts that restriction. It lifts it for the requester only, and only for the connector the request names. Every other restriction still applies to them, including ones added to their role later. Before you approve, the dialog names the connector and the person it opens for.

Every other kind of request records your decision and changes nothing by itself. For example, approving a request about a missing permission does not give anyone a role. Give the person the role or grant separately. The record then shows that you reviewed the request.

Denying a request always records a decision only.

Warning

An administrator cannot decide their own request. The person who asks and the person who answers must be two different people, because an approval you signed yourself looks the same downstream as one a second person signed. Another administrator must decide it.

Withdraw your own request

  1. Open Governance → Access requests.
  2. Find your Pending request.
  3. Choose Withdraw, then confirm.

You need no permission for this. Withdrawing is a statement about your own ask, not a decision on it. An administrator uses it to close a request of their own that they no longer need.

What to know

  • Filing, deciding and withdrawing a request are all recorded in the audit log.
  • Only a Pending request can be decided or withdrawn.
  • A request about a restriction tells an administrator that someone was blocked. It never tells the requester which rule blocked them.