GOVERNATLAS / PRODUCT DOSSIER

Omada Identity Cloud

Omada describes Identity Cloud as an as-a-service IGA offering covering identity lifecycle, access governance, provisioning and risk analytics. Omada describes role mining, anomaly detection and usage-based access recommendations, with configurable connectors and an assistant that can initiate access reviews.

01 / CONTEXT & SCOPE

Understand the proposition.
Define the boundary.

Where it fits

Evaluate the operating model as well as the recommendation.

The decision to make

Evaluate the operating model as well as the recommendation. Cloud delivery still leaves the buyer responsible for source ownership, connector privileges, correlation rules and exception decisions. Ask how an assistant-initiated review is authorized and recorded. Keep role suggestions distinct from approved role changes and actual target-system permissions.

What this record does not establish

Implementation-time promises and percentage improvements are excluded as GovernAtlas results. Vendor cloud-architecture statements do not establish the buyer’s contracted residency, isolation, retention or recovery arrangement.

1 current source · 2 published assertions
Source coverage is a research boundary, not a quality score.

02 / YOUR EVALUATION

Turn interest into a useful trial.

Open the evaluation playbook ↗
A

A test worth running

Use a synthetic business unit with a known role pattern and one justified exception. Inspect a suggested role, reject an inappropriate recommendation and preserve the rationale. Initiate a bounded review through the proposed interface, then introduce stale usage data. Compare the displayed context with collection times and check that missing evidence is visible to the decision owner.

GovernAtlas editorial proposal. We have not performed this test.

B

Evidence to bring back

  1. A role recommendation with input provenance, human disposition and an explicit exception.
  2. The authorized review trigger, collection freshness and target-change evidence for the selected connectors.

THE OPERATING DETAIL

Follow the decision into the enforcing system.

GovernAtlas analysis: practical review considerations, not findings from a product test.

Set the operating boundary

Cloud delivery still leaves the buyer responsible for source ownership, connector privileges, correlation rules and exception decisions. Ask how an assistant-initiated review is authorized and recorded. Keep role suggestions distinct from approved role changes and actual target-system permissions.

A proposed buyer demonstration

Use a synthetic business unit with a known role pattern and one justified exception. Inspect a suggested role, reject an inappropriate recommendation and preserve the rationale. Initiate a bounded review through the proposed interface, then introduce stale usage data. Compare the displayed context with collection times and check that missing evidence is visible to the decision owner.

What the evidence does not establish

Implementation-time promises and percentage improvements are excluded as GovernAtlas results. Vendor cloud-architecture statements do not establish the buyer’s contracted residency, isolation, retention or recovery arrangement.

03 / DOCUMENTED EVIDENCE

Read the claim. Inspect the basis.

Each statement retains its classification and preserved source. A vendor assertion is not an independent test result.

01
vendor asserted

Omada describes role mining, anomaly detection and usage-based access recommendations, with configurable connectors and an assistant that can initiate access reviews.

Source, dates & preserved provenanceOmada Identity Cloud — current primary scope ↗

Authority: vendor owned
Observed 2026-10-18 · Reviewed 2026-10-18 · current until 2026-11-17

Artifact SHA-256: 610cd08559f625ebb324f56a6b4f1ddfe45516caceec6f8104133fae7bff0901

The hash identifies the preserved capture. The live source may have changed.

02
vendor asserted

Omada describes Identity Cloud as an as-a-service IGA offering covering identity lifecycle, access governance, provisioning and risk analytics.

Source, dates & preserved provenanceOmada Identity Cloud — current primary scope ↗

Authority: vendor owned
Observed 2026-10-18 · Reviewed 2026-10-18 · current until 2026-11-17

Artifact SHA-256: 610cd08559f625ebb324f56a6b4f1ddfe45516caceec6f8104133fae7bff0901

The hash identifies the preserved capture. The live source may have changed.

Source register

Omada Identity Cloud — current primary scope ↗vendor owned · captured 2026-10-18
Brand asset provenance

Organization identity asset from its official website; inclusion does not imply endorsement.

Official website ↗ · Original asset ↗

04 / BEFORE YOU COMMIT

Better questions.
A clearer decision.

Resolve these with the provider and your own evaluation team.

01

Can you demonstrate and export: A role recommendation with input provenance, human disposition and an explicit exception.

02

Can you demonstrate and export: The authorized review trigger, collection freshness and target-change evidence for the selected connectors.

Regulatory applicability requires a separate, current determination. Inclusion is not certification.

COMPLIANCE / CLAIMS, SCOPE & GAPS

Start with the requirement.
Inspect the support.

Prepare your vendor review ↗

These labels describe this dossier’s current evidence coverage. A published mention may be a framework mapping, a qualified assertion or a limitation; it is not a compliance finding.

For HIPAA-regulated use, request service-specific BAA eligibility, processing scope and responsibility details. Missing evidence here does not establish noncompliance. Payment cannot alter these evidence labels.

KEEP THE RECORD USEFUL

A dossier should stand up to scrutiny.

Have a source that changes this picture? Submit it for editorial review.

Raise an evidence issue ↗