Provisioning AI tools: SCIM for ChatGPT, Claude, Cursor and the rest
AI assistants spread through a company faster than any app before them. What the Okta catalog shows about sign in and provisioning for AI tools, and how to keep access governed.
Thomas Bieser, Cofounder and CEO ·
No category of software has spread through companies as fast as AI assistants. A team starts on a monthly plan, then another team signs up, then someone connects the assistant to a shared drive. Within a quarter there are dozens of accounts, some on personal emails, and nobody is sure who still has access.
Why AI tools need lifecycle control more than most apps
- They hold sensitive content. Prompts, uploaded files and conversation history often include customer data and source code.
- They connect to other systems. Assistants increasingly reach into drives, ticketing and code repositories on a user's behalf.
- They start bottom up. Accounts are created before IT knows the tool exists, so there is no provisioning, and no deprovisioning either.
When someone leaves, their AI account, its history and its connections should end that day.
What the Okta catalog shows
From our November 2026 research on the Okta Integration Network:
- Claude is listed with SAML sign in and Cross App Access, Okta's model for governing how AI agents connect to other apps.
- Cursor is listed with SAML sign in.
- OpenAI's vendor listing is an Okta Workflows connector, not a sign in or provisioning integration.
Catalog listings describe what an integration supports, not which plan of the tool includes it. AI vendors commonly reserve SSO and SCIM for enterprise contracts, so check the plan each team actually bought.
A practical policy for AI tools
- Find the accounts. List every AI tool in use and who administers each workspace.
- Consolidate workspaces. One company workspace per tool, owned by IT.
- Require sign in through your identity provider where your plan allows it.
- Automate joiners and leavers. Assign the tool by group, and remove the account on the last day.
- Review quarterly. Who has access, which connections they created, and whether they still need it.
When the plan does not include SCIM
Upgrading every team to an enterprise contract to get SCIM is the SCIM tax again, applied to the fastest growing line in your software budget. StitchOps carries your identity provider's joiner, mover and leaver events into the tool's admin console on the plan you have, anywhere a person can log in and act, and logs every change. Your identity provider stays the source of truth.
StitchOps is also a resource app in Okta's Cross App Access ecosystem, so agents can reach governed work under Okta policy. See pricing.
Frequently asked questions
- Do AI assistants support SCIM provisioning?
- Some do, usually on enterprise contracts. Check the plan you are on. Many teams start on a team plan where SSO or SCIM is not included.
- What does the Okta catalog show for AI tools?
- In our November 2026 research, the Claude listing supports SAML and Cross App Access, the Cursor listing supports SAML, and the OpenAI vendor listing is an Okta Workflows connector rather than a sign in or provisioning integration.
- Why does provisioning matter more for AI tools?
- AI tools hold prompts, files and connections to other systems. When someone leaves, their account and the integrations it owns should end that day.
- How do we govern AI tools without enterprise contracts?
- StitchOps carries your identity provider's joiner, mover and leaver events into the tool's admin console on the plan you have, anywhere a person can log in and act, and logs every change.
ChatGPT and OpenAI are trademarks of OpenAI. Claude is a trademark of Anthropic. Cursor is a trademark of Anysphere. Okta is a trademark of Okta, Inc. Listing details are from StitchOps' review of the public Okta Integration Network catalog on November 17, 2026. Vendor plans change often; check current terms.