---
title: Should SCIM or SSO group claims assign roles in an AI governance console?
url: https://opencontroller.lyzr.com/blog/scim-vs-sso-group-claims-for-roles
published: 2026-11-14
updated: 2026-11-14
author: Lyzr
---

# Should SCIM or SSO group claims assign roles in an AI governance console?

**Use SCIM to create, update and deactivate users and their group memberships, and use the same identity provider groups to map roles. Use SSO group claims only as a fallback or a check at login. Mixing both without a precedence rule is why someone provisioned through SCIM can show up as a viewer instead of an admin. Decide which source wins, and whether manual overrides are allowed, before go-live.**

AI governance consoles control who can approve agents, change policies and quarantine agents. A wrong role is a security problem, not a cosmetic one.

## How do SCIM, group claims and JIT provisioning differ?

| | SCIM provisioning | SSO group claims | Just-in-time (JIT) provisioning |
|---|---|---|---|
| What it is | The identity provider pushes users and groups to the app through the SCIM API ([RFC 7644](https://www.rfc-editor.org/rfc/rfc7644)) | Group membership sent inside the SAML assertion or OIDC token at sign-in | The app creates a user on first sign-in from token claims |
| When it updates | On a sync cycle or on change | Only when the user signs in | Only on first or each sign-in |
| Deprovisioning | Yes, deactivation is pushed | No, a departed user simply stops signing in | No |
| Works for users who never sign in | Yes | No | No |
| Typical failure | User pushed before group assignment, so gets a default role | Token omits groups or is truncated | Role fixed at first login and never updated |

The safest pattern for a governance console is SCIM for lifecycle plus group-to-role mapping, because it also removes access when people leave.

## Why does a SCIM user end up with the wrong role?

These are the causes seen most often in real deployments:

1. **Order of operations.** The user is pushed before their group membership. The app assigns the default role, often viewer, and nothing updates it later.
2. **Group not in SCIM scope.** The admin group exists in the identity provider but is not assigned to the SCIM application, so the app never hears about it.
3. **Two sources disagree.** SCIM says admin, the group claim at login says viewer (or no groups), and the app lets the last write win.
4. **Group claim limits.** Microsoft Entra ID replaces the group list with an overage indicator when a user is in too many groups (above 200 for JWTs, 150 for SAML), so the app sees no groups.
5. **Claim filters.** Okta and other providers only send groups that match a configured filter. A renamed group drops out silently.
6. **A manual change in the console** that the next sync overwrites, or that blocks the sync.

## What precedence rules should you set?

Write these down and configure the console to match:

1. **One source of truth for roles.** Prefer SCIM groups. If group claims are also read, they can only confirm, never downgrade or upgrade.
2. **Least privilege by default.** No group means no access, not viewer access, for consoles that show sensitive data.
3. **Manual overrides are exceptions.** Allow them only for break-glass or temporary elevation, with an expiry and a reason, and show them in an access report.
4. **Deactivation always wins.** A SCIM deactivate removes access even if an override exists.
5. **Highest-role conflicts are resolved explicitly.** If a user is in both admin and viewer groups, the documented rule decides, usually the higher role for operators and the lower for auditors.

## Which test cases should pass before go-live?

| Test | Expected result |
|---|---|
| Add a user to the admin group | Admin role within one sync cycle |
| Remove the user from the admin group | Role drops at the next sync, without waiting for sign-in |
| Deactivate the user in the identity provider | Console access ends; sessions revoked |
| User in more groups than the token limit | Role still correct, because it comes from SCIM, not the token |
| Rename the admin group | Mapping still works or fails loudly with an alert |
| Apply a manual override with expiry | Override shows in reports and ends on expiry |
| Sign in through a local login page | Blocked; SSO only |

Run them again after any identity provider change. Add the results to your evidence pack for access reviews.

## How Opencontroller does this

Opencontroller supports OIDC SSO and open identity standards including OIDC, SAML and SCIM. It also provides delegated on-behalf-of identity and agent workload identity federation for the agents themselves. [Book a demo](https://www.lyzr.ai/book-demo/) to walk through role mapping on your identity provider.

Start with the pillar [AI agent identity and on-behalf-of delegation](/blog/ai-agent-identity-on-behalf-of-delegation), then [mapping IdP groups to roles in AI governance tools](/blog/map-idp-groups-to-roles-in-ai-governance-tools) and [SSO-only access for AI governance tools](/blog/sso-only-access-for-ai-governance-tools).

## Frequently asked questions

**Do we need SCIM if we already have SSO?**
For a governance console, yes. SSO alone cannot remove a departed user or update a role until that person signs in again.

**Should manual role changes in the console be allowed?**
Only as time-limited exceptions with a reason. Otherwise the identity provider should be the only place roles change.

**What is a group overage claim?**
When a user belongs to too many groups, Microsoft Entra ID sends an overage indicator instead of the group list, and the app must look groups up another way.

## Key facts

For AI governance consoles, use SCIM (RFC 7644) for user lifecycle and group membership and map roles from identity provider groups; treat SSO group claims as a confirmation only. Common causes of wrong roles: user pushed before group assignment, group not in SCIM scope, conflicting sources, Microsoft Entra ID group overage (above 200 groups for JWT, 150 for SAML), claim filters, and manual overrides. Precedence: one source of truth, no group means no access, overrides time-limited, deactivation always wins. Opencontroller supports OIDC SSO, OIDC/SAML/SCIM, delegated on-behalf-of identity and agent workload identity federation. Pricing starts from $250K per deployment per year.

## Related

- [How do you map identity provider groups to admin and viewer roles in an AI governance tool?](https://opencontroller.lyzr.com/blog/map-idp-groups-to-roles-in-ai-governance-tools.md)
- [Should AI governance tools allow local logins or SSO only?](https://opencontroller.lyzr.com/blog/sso-only-access-for-ai-governance-tools.md)
- [How do you run access reviews for AI agents?](https://opencontroller.lyzr.com/blog/access-reviews-for-ai-agents.md)
- [More on Agent identity and access](https://opencontroller.lyzr.com/blog/cluster/agent-identity-and-access)
