---
title: How should manual role overrides work when roles come from SCIM?
url: https://opencontroller.lyzr.com/blog/manual-role-overrides-with-scim-provisioning
published: 2026-11-14
updated: 2026-11-14
author: Lyzr
---

# How should manual role overrides work when roles come from SCIM?

**Let the identity provider stay the source of truth, and treat a manual override as a time-limited exception layered on top of it. Store the override separately from the SCIM-provisioned role, give it an owner, a reason and an expiry, make sure the next sync does not silently erase or keep it, and log every change. Then fix the group mapping in the identity provider so the override can expire.**

SCIM (System for Cross-domain Identity Management, RFC 7643 and RFC 7644) lets an identity provider create, update and deactivate users and groups in an application automatically. In AI governance tools, groups usually map to roles such as admin, approver and viewer. It works well until someone who should be an admin appears as a viewer on the morning of a go-live. This guide sits under our [guide to agent identity and on-behalf-of delegation](/blog/ai-agent-identity-on-behalf-of-delegation).

## Why do SCIM roles come out wrong?

The cause is almost always upstream of the application:

- The user is not in the expected group in the identity provider.
- The group is assigned to the app but not pushed, so the app never receives membership.
- Two groups map to different roles and the app resolves the conflict differently from what you expected.
- Group names changed in the identity provider and the mapping still points to the old name.
- The user was provisioned before the mapping existed and no update has been pushed since.

A manual override fixes the symptom. It should never be the fix.

## What precedence rules should apply?

Decide these before go-live and document them.

| Situation | Recommended behaviour |
|---|---|
| Active override exists | Effective role is the override until it expires |
| Override expires | Effective role reverts to the SCIM-provisioned role |
| SCIM deactivates the user | Deactivation wins; the override is removed |
| SCIM grants a higher role than the override | Use the higher role and close the override |
| Several groups map to different roles | Highest privilege wins, or a defined order; never undefined |

The most important rule is the third. Deprovisioning from the identity provider must always win. An override that keeps a leaver's admin access alive defeats the purpose of SCIM.

## How should overrides be stored?

Keep the SCIM-provisioned role and the override in separate fields. If an override simply overwrites the role field, the next sync either erases it without warning or, worse, the app stops accepting updates for that user. Separate fields make the effective role a calculation: provisioned role, plus any active override, minus anything a deactivation removes.

Each override record should hold:

- user, provisioned role and override role
- reason, with a link to the ticket
- who approved it and who applied it
- start time and expiry time
- status: active, expired or revoked

## How long should an override last?

Short. Days, not months. The override exists to unblock someone while the group mapping is fixed. Seven to fourteen days is a common range. Send a reminder to the approver before expiry. If the same override is renewed twice, that is a signal the mapping was never fixed.

Restrict who can create overrides. A small set of administrators, ideally not the people receiving the override, keeps segregation of duties intact. Our post on [segregation of duties for AI agent approvals](/blog/segregation-of-duties-for-ai-agent-approvals) covers why that matters for approver roles.

## What about break-glass access?

Keep one or two break-glass admin accounts that do not depend on the identity provider, stored in a vault and monitored. They exist for when SSO or SCIM is down, not for routine role fixes. Every use should raise an alert. This is separate from the override process, though both need the same audit trail.

## What should be audited?

Log every override created, changed, expired or revoked, with the fields above. Log the effective role at each sign-in, and log every SCIM event that touched the user. When an auditor asks why someone had admin rights on a given date, you should be able to answer from the log in one query.

Review open overrides at each access review. Our guide to [access reviews for AI agents](/blog/access-reviews-for-ai-agents) explains the cadence, and [mapping identity provider groups to roles](/blog/map-idp-groups-to-roles-in-ai-governance-tools) covers the upstream fix.

## How Opencontroller does this

Opencontroller supports OIDC SSO and open identity standards including OIDC, SAML and SCIM, with delegated on-behalf-of identity for agents. Access to the console can be tied to your identity provider so that roles follow group membership. See the [capability reference](/capability-reference) or [book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**Will the next SCIM sync overwrite a manual role change?**
It depends on the application. If the override is stored in the same field as the provisioned role, a sync can erase it. Store overrides separately so sync behaviour is predictable.

**Should a manual override survive deprovisioning?**
No. Deactivation from the identity provider should always remove the user and any override.

**How long should a manual role override last?**
Days, not months. Long enough to fix the group mapping in the identity provider, with an expiry and a reminder before it lapses.

## Key facts

- SCIM is defined in RFC 7643 (schema) and RFC 7644 (protocol).
- Store manual role overrides separately from SCIM-provisioned roles, with owner, reason, approver and expiry.
- Deprovisioning from the identity provider must always remove the user and any override.
- Overrides should last days, not months; repeated renewals signal an unfixed group mapping.
- Keep break-glass admin accounts separate from the override process, vaulted and alerted.
- Opencontroller supports OIDC SSO and open identity standards (OIDC, SAML, SCIM) with delegated on-behalf-of identity.
- Opencontroller starts from $250K per deployment per year.

## Related

- [Should SCIM or SSO group claims assign roles in an AI governance console?](https://opencontroller.lyzr.com/blog/scim-vs-sso-group-claims-for-roles.md)
- [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)
- [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)
