Skip to content

Set the rules for AI once, for every AI app

Choose what each role or person’s AI can do in each app, down to single actions. The same rules hold in ChatGPT, Claude, Cursor and Microsoft Copilot, and every action it takes in your apps is logged.

  • Free 14-day trial
  • No credit card
  • Free plan for one person
Claude Elaichi connected

Delete the HubSpot contacts who unsubscribed last year.

AP

Checking HubSpot with Elaichi

  • Found 312 unsubscribed contacts in HubSpot
  • Delete a contact Restricted for your role

I found 312 contacts, but I can’t delete them: deleting contacts is restricted for your role. Want me to ask an admin for access?

Three people, three kinds of rule

A rule for a role, a rule for one person, and a seat that can only read.

JM SupportJake Morgan

“Give Acme Corp 50% off their next invoice.”

Claude
Found Acme Corp in Stripe
Create a couponRestricted for your role

Look up customers, create no coupons

A rule on Jake’s role restricts Create a coupon in Stripe and leaves the reads open. His AI finds the customer, says the tool is restricted for his role, and offers to ask an admin for access.

Uses Stripe

CB Engineering contractorChris Bennett

“What’s blocking the release in Jira?”

Cursor
Searched open issues in the release project
Read the release checklist in Confluence
Create or edit issuesRestricted for your account

A contractor who can only read

An admin adds a rule just for Chris that allows only the read tools in Jira and Confluence. A rule for one person can only narrow what the role allows, so reads are all his AI can do.

Uses Jira Confluence

LH ComplianceLauren Hughes

“Show me every Salesforce action from last week.”

ElaichiAudit log
Emily Carter looked up Acme Corp, from ChatGPT
Megan Brooks updated a deal stage, from Claude

Evidence on request

The compliance team gives the reviewer a free Auditor seat. She reads the audit log and the setup, filtered by person, action and date, but can’t run a tool or change a rule.

Uses Salesforce

Rules before each call, a record after

What AI control looks like without Elaichi

  • When a team shares one key, every call shows up as that one key.
  • AI apps are often handed every action an app offers, delete included.
  • To answer an auditor, you pull records from each app, one at a time.

With Elaichi

  • Give each person one role: one of eight built in, or your own.
  • Restrict whole apps or single actions, for a role or for one person. A restricted action can’t be run from any AI app.
  • A new rule reaches every AI app within about two minutes.
  • Someone who needs more can ask from their AI app. An admin approves it for that one person, and nothing else changes.
  • Every tool call that runs is logged with who made it, the app, the account and the AI app.

Set it up in four steps

In the order an admin takes them.

  1. 1

    Give everyone one role

    Start from the eight built-in roles, from Guest to Org Owner, or build your own from the permission list. Each person holds exactly one.

  2. 2

    Restrict what matters

    Allow or restrict whole apps or single tools, for a role or for one person. A rule for one person can only narrow the role’s, and a restriction always wins over an allow.

  3. 3

    Let people ask for more

    Someone who hits a restriction can file an access request, even from their AI app. Approving it opens that app or tool for that one person only.

  4. 4

    Read the record

    Review every call that ran in the audit log, filtered by person, action and date. Give reviewers a free, read-only Auditor seat.

For IT and engineering

Governance in Elaichi has three parts. Roles decide what each person may do: eight built-in roles or your own, one role per person. Restrictions decide which apps and single tools each role or person can use, and a restricted tool can’t be run, whatever a prompt says. The audit log records every tool call that runs, whether it worked or failed, with the person, the account it reached and the AI app it came from.

Details that matter

  • Rules follow the action, not the name. Restrictions check the catalog tool’s own name and operation, so renaming a tool inside a toolbox never gets it past a rule.

  • Restricted means it can’t run. A restricted tool can’t be run. If the AI searches for it, search names it as restricted, with no description and no way to call it.

  • Values stay out of the log. The log records no argument names, counts or values, except the id of the record a call targets, often with its title and a link. A failed call is logged with a fixed error code, not the other app’s own error text.

  • Your log, in your Datadog. Elaichi keeps the audit log for 90 days on every plan. On Black, you can also forward it to your own Datadog.

Three ways to control what AI can do

Aspect Shared keys Each AI app’s own settings Elaichi
Who can act Whoever holds the key Whoever has the app set up One role per person, built in or your own
What the AI can run Everything the key can reach Set in each AI app Only allowed tools; restricted ones can’t be run
Where the rules live Wherever the key went In each AI app, separately In one place, for every AI app
Changing a rule Change keys and set up again Edit each AI app’s settings Edit it once; it lands within about two minutes
The record Under one shared key Varies by AI app Each call that runs, with the person, account and AI app

Questions, answered

Can I choose which actions the AI can use?

Yes. Rules work on single tools, not only whole apps. Allow or restrict apps and tools for a role or for one person; a rule for one person can only narrow the role’s. A restricted tool can’t be run, and search shows it only as restricted.

What happens when someone’s AI tries a restricted action?

It is refused. The AI is told the tool is restricted for their role or for their account, and that an admin can lift it through an access request, which the AI can file for them.

Can I give a compliance reviewer access without paying for a seat?

Yes. The Auditor role is read-only and free. A reviewer can read the log and the setup without a paid seat and without being able to change anything.

What does the audit log record for each call?

One entry for every tool call that runs, whether it worked or failed: the person, the tool, the account it reached, the AI app it came from, how it was approved and the outcome. A call refused before it runs, for example by a restriction, writes no entry. Argument values are not recorded, except the id of the record a call targets.

Can I tell which AI app made a call?

Yes. Each entry records where the call came from and the AI app’s name, such as Claude, ChatGPT or Cursor. An AI app Elaichi can’t verify shows the name it gave itself.

Can’t I set these rules in each AI app’s admin settings?

Each AI app has its own controls, set and kept up app by app. Elaichi sets roles and per-tool restrictions once for every AI app that connects, and keeps one audit log across them. An AI app sees Elaichi as one server, so control over the apps and tools behind it is set in Elaichi.

How do restrictions work between a role and a person?

Restrictions target a role or one person. A rule for one person can only narrow what the role allows, a restriction always wins over an allow, and with no rules everything is open, so you narrow access on purpose.

How long until a new restriction takes effect?

Within about two minutes, in every AI app. Removed shares and suspended members take effect on the next request.

Can I send the audit log to my own SIEM?

On Black, you can forward it to your own Datadog. On every plan, the audit log stays in Elaichi for 90 days, searchable by person, action and date.

Who approves what an AI app can do?

Each person approves an AI app when they connect it, on Elaichi’s consent screen. “Use your connected apps” covers every tool they can use, deletes in your apps included; the other boxes cover Elaichi’s own data, and delete is never pre-ticked. To hold an AI app to certain tools, use restrictions or connect it to chosen toolboxes.

Set your first rule

Start a trial, restrict one action for one role, and watch it hold in every AI app.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot