“Pull my open deals from HubSpot.”
Off in the identity provider, off in every AI app
IT turns Tyler off in the identity provider. SCIM suspends him in Elaichi, and every AI app he connected is refused on its next request.
People join through the sign-in your company already uses, with the right role from the start. When someone leaves, one step cuts off every AI app they connected to Elaichi, on its very next request.
What should I pick up first this sprint?
RHDay one · checking 2 apps with Elaichi
Start with ENG-1207, the sign-in bug. It’s marked urgent, and the onboarding page says new engineers pair on it with their team lead.
What happens when someone leaves, when an admin removes them, and when someone asks about them later.
“Pull my open deals from HubSpot.”
IT turns Tyler off in the identity provider. SCIM suspends him in Elaichi, and every AI app he connected is refused on its next request.
“Kevin is leaving. Remove him for good.”
Before the removal goes through, Elaichi lists what others rely on, like a private connection a shared toolbox uses. Lauren hands HubSpot to Ashley Parker, and the rest is deleted with Kevin. Toolbox entries Kevin set up need a quick re-pin afterward.
“What did people who left do last week?”
The audit log keeps every call that ran for 90 days. People who have left show as Former member, so their record stays readable.
How access usually gets handed out
With Elaichi
In the order an admin takes them.
Prove you own your email domain with a DNS record. People on it can then join on their own, with a default role you choose.
Add SAML or OIDC single sign-on, built into Elaichi, and require it for email sign-ins on your domain.
Sync people and groups with SCIM 2.0 and map a group to a role. Turning someone off in your identity provider suspends them in Elaichi.
When someone leaves for good, remove them in Elaichi. The check lists what others rely on, and the removal goes through once each item is transferred or deleted.
Elaichi follows the system your company already uses to manage accounts, called an identity provider. People join through SAML or OIDC single sign-on, SCIM, a verified email domain or an invite, and arrive with a role. When your identity provider deactivates someone, SCIM suspends them in Elaichi and revokes every AI app connection they hold, so each one is refused on its next request. Removing someone for good is a separate step, with a check that asks you to decide on what others rely on first.
SCIM suspends; an admin removes. Turning a user off in your identity provider suspends them in Elaichi. Turning them back on restores the membership, and each AI app connects again with fresh consent. Removing a member is a separate step an admin takes, so a sync mistake never deletes anyone’s work.
Ending access isn’t cached. AI app connections are checked on every request, so a suspension or removal takes effect on the next one. Roles, restrictions and teams ride a short cache and land within about two minutes.
Private stays private. A private connection that nothing else depends on is deleted with its owner, not handed to someone else. If a shared toolbox relies on one, the admin decides whether to transfer or delete it first.
Try it in the trial. Every new workspace starts with a 14-day Black trial, no credit card needed, with single sign-on, SCIM and group-to-role mapping included. Gold and Black both include them.
| Aspect | By hand | Identity provider alone | Elaichi with your identity provider |
|---|---|---|---|
| Joining | Accounts set up app by app | Sign-in for the apps it covers | Arrive with a role through SSO, SCIM, a domain or an invite |
| Roles | Granted person by person | Per app, where the app supports it | Mapped from identity provider groups |
| Leaving | Access removed app by app | Sign-in ends for the apps it covers | Suspended; every AI app they connected is refused on its next request |
| Shared work | Reassigned by hand | Reassigned app by app | A check before removal lists what others rely on |
| Proof it ended | A manual checklist | The identity provider’s sign-in log | Every call that ran, in the audit log for 90 days |
Decide what each role or person’s AI can do, down to single actions, and see every call that runs.
Read moreShare an app with your team, not the login. Each person uses it from their own AI.
Read moreConnect each app once and use it from ChatGPT, Claude, Cursor, Microsoft Copilot or any MCP client.
Read moreSee the whole picture in the product tour and the security model.
On their next request. Suspending or removing them, by hand or through SCIM, revokes every AI app connection they hold, and each one is refused on its next request.
Not once they are suspended. Paid seats are active members, so suspended members, along with free roles such as Auditor and Guest, don’t count.
Single sign-on decides who can sign in. Elaichi uses your identity provider for that, and adds roles for what each person’s AI can do in your apps. When someone is turned off, every AI app they connected through Elaichi is refused on its next request.
No. A SCIM deactivation or delete suspends the member and revokes their AI app connections. Turning them back on restores the membership, and their AI apps connect again with fresh consent. Removing a member for good is a separate step an admin takes.
Elaichi supports SAML and OIDC for single sign-on and SCIM 2.0 for provisioning, so an identity provider that speaks those standards should work. Elaichi’s single sign-on is built in, with no third-party sign-in vendor in the path.
No. A SCIM group mapping sets at most one role and never sets teams. Invites can preset teams, and an admin adds people who join any other way.
Within about two minutes. Roles, restrictions and teams ride a short cache. Suspensions, removals and removed shares take effect on the next request.
Yes. Every new workspace starts with a 14-day Black trial, no credit card needed, with single sign-on, SCIM and group-to-role mapping included.
Start a trial, connect single sign-on or SCIM, and see a suspension take effect on the very next request.
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