# Automated provisioning and deprovisioning | Elaichi

> Onboard people into the right role through SSO and SCIM, and offboard in one action. Removing a member revokes every live grant on the next call.

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?”
>
> Ryan Hayes, Engineering, in Cursor

- Done: Found 4 issues assigned to you in Jira
- Done: Read the team’s onboarding page
- Can’t: Delete issues (Restricted for your role)

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.

## Their last day, and the days after

What happens when someone leaves, when an admin removes them, and when someone asks about them later.

### Off in the identity provider, off in every AI app

> “Pull my open deals from HubSpot.”
>
> Tyler Reed, Operations, in ChatGPT

- Refused: Elaichi: “You are no longer an active member of this organization.”

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.

### A removal that checks first

> “Kevin is leaving. Remove him for good.”
>
> Lauren Hughes, IT, in Elaichi: Remove Kevin Ward

- Done: HubSpot, used by a shared toolbox: transfer to Ashley Parker
- Done: 2 private connections nothing else uses: delete

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.

Connectors: [HubSpot](https://elaichi.ai/connectors/hubspot/)

### A record that stays after they go

> “What did people who left do last week?”
>
> Brian Foster, Security, in Elaichi: Audit log

- Done: Former member searched contacts in HubSpot
- Done: Former member posted in #ops in Slack

The audit log keeps every call that ran for 90 days. People who have left show as Former member, so their record stays readable.

Connectors: [HubSpot](https://elaichi.ai/connectors/hubspot/), [Slack](https://elaichi.ai/connectors/slack/)

## Arrive ready, leave clean

### How access usually gets handed out

- Accounts are set up by hand, one app at a time.
- When someone leaves, each app is switched off in its own admin console.
- AI apps connected on the side are easy to miss.

### With Elaichi

- People join through single sign-on, SCIM, a verified domain or an invite, with a role set from the start.
- An invite can also put them in their teams. People who join any other way are added to teams by an admin.
- Suspend or remove someone, by hand or through SCIM, and every AI app they connected is refused on its next request.
- Removing someone for good asks you to decide on what others rely on first.
- Suspended people don’t count as paid seats.

## Set it up in four steps

1. **Verify your domain.** 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.
2. **Connect single sign-on.** Add SAML or OIDC single sign-on, built into Elaichi, and require it for email sign-ins on your domain.
3. **Turn on SCIM.** 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.
4. **Remove with the check.** 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.

## For IT and engineering

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.

### Details that matter

- **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.

### Three ways to manage who has access

| | 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 |

## Related use cases

- [Control what AI can do](https://elaichi.ai/use-cases/governance/): Decide what each role or person’s AI can do, down to single actions, and see every call that runs.
- [Share apps without sharing logins](https://elaichi.ai/use-cases/context-sharing/): Share an app with your team, not the login. Each person uses it from their own AI.
- [Connect apps once, not once per AI app](https://elaichi.ai/use-cases/connect-once/): Connect each app once and use it from ChatGPT, Claude, Cursor, Microsoft Copilot or any MCP client.

## Further reading

- [Offboarding AI access, contractors included](https://elaichi.ai/blog/offboarding-when-the-agent-holds-access/)
- [SCIM and AI agents: where provisioning stops](https://elaichi.ai/blog/identity-provider-scim-vs-mcp-grants/)
- [How to roll out Claude and ChatGPT to employees](https://elaichi.ai/blog/roll-out-claude-and-chatgpt-to-employees/)
- [Designing roles for AI agents: one role each](https://elaichi.ai/blog/designing-roles-for-ai-agents/)
- [HR can read Rippling in Claude, not run payroll](https://elaichi.ai/blog/hr-team-claude-rippling-employees/)

## Frequently asked questions

### How fast does access end when someone leaves?

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.

### Do we keep paying for people who have left?

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.

### What happens to shared toolboxes when someone leaves?

When an admin removes them, Elaichi asks for a decision on each shared toolbox, template and private connection others rely on: transfer it to another member or delete it. Custom connectors they own must be transferred. Shared connections stay in place unless you transfer or delete them, and toolbox entries the person set up need a re-pin afterward.

### Doesn’t single sign-on already cover AI apps like ChatGPT and Claude?

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.

### Does SCIM delete the member in Elaichi?

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.

### Which identity providers can manage access?

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.

### Does SCIM put people into teams?

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.

### How long until a role change takes effect?

Within about two minutes. Roles, restrictions and teams ride a short cache. Suspensions, removals and removed shares take effect on the next request.

### Can we test single sign-on and SCIM before paying?

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.

See also [Product](https://elaichi.ai/product/) and [Security](https://elaichi.ai/security/), or [start a trial](https://app.elaichi.ai/signup).
