Security
The security controls available at the organization level.
Beyond role-based access, an organization has a handful of controls over how people and systems authenticate into it at all.
Single sign-on
An organization can connect its own identity provider so members sign in through it instead of a separate Auron credential. This is useful for organizations that already centralize authentication and want Auron to follow the same policy, including anything that policy enforces, such as MFA.
SCIM provisioning
For organizations that manage user lifecycle centrally, SCIM lets an identity provider create, update and deactivate Auron users automatically as people join or leave, instead of someone doing it by hand inside Auron.
API keys and OAuth clients
Access issued outside a human sign-in, API keys, and OAuth2 connections like Auron in Claude, is scoped and revocable independently of any user's own session. Cutting off a script or a connector doesn't require touching anyone's account.
Where this is managed
These settings live in the console alongside the rest of Organization settings.