Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Govern access

OpenIAM's identity governance surface — access certification campaigns and segregation of duties, two independent subsystems that share a data model only at the edges.

Applies to: OpenIAM 2026.9.1

What this is, and when you need it

This is OpenIAM's identity governance (IGA) surface. This section is for the administrator who has to prove that the access people hold is the access they should hold — to an auditor, a regulator or an internal control owner.

Governance in OpenIAM is two independent subsystems, plus risk scoring alongside them. You can adopt one without the others.

Subsystem
What it answers
Where

Access certification

Is the access people already hold still justified? Periodic review campaigns, which reviewers meet in SelfService

Segregation of duties

Does anyone hold a combination they should not? Toxic-combination detection, policies, rule sets, mitigations

Risk scoring

Which access deserves attention first? A 0–100 score per entitlement, membership and identity

Caddie — Access Review Assistant

What does a reviewer need to know to decide this line? A read-only context panel beside each review row, and the audit trail of every item

They meet in exactly two places. A campaign can narrow its scope by membership risk score, and a reviewer sees the SoD violations attached to an item through ACCESS_REVIEW_ITEM_SOD_VIOLATION — which can block that item's decision until the violation is resolved. Everything else is independent.

Read Change configuration safely once before your first change.

Where to start

If you need to…
Go to

Run a periodic access review and produce evidence for it

Detect and work toxic combinations of access

Score access by risk, and feed that into either of the above

Three shipped defaults that decide whether governance works

Where the objects live

Certification has its own database. CERTIFICATION, CERTIFICATION_REVIEWER, CAMPAIGN, CAMPAIGN_STEP, CAMPAIGN_REVIEWERS, CAMPAIGN_PREVIEW_EXCLUSION, ACCESS_REVIEW_ITEM and its child tables live in a database of their own, reached over jdbc.certification.url and named certification unless your deployment overrode it. Risk and SoD objects stay in the openiam schema. A join across the two in a hand-written report is a cross-database join — plan for it. The Webconsole never shows you which database it is reading from, so if you need the live connection string, ask the deployment owner.

Last updated

Was this helpful?