Topic starter
24/06/2026 10:30 pm
TL;DR: Easier access request configuration, full visibility into child assignment status for reviewers, and Docker-based Cloud Application Gateway deployment are among the additions in Omada Identity Cloud’s April 2026 release, according to Omada Identity. These changes tighten governance workflows, but they do not remove the need for disciplined lifecycle controls and review design.
Editorial analysis by NHI Mgmt Group, based on content published by Omada Identity: “Product News”.
Key questions
Q: Why does child assignment visibility matter in access reviews?
A: Because reviewers need to see the access that actually exists, not only the top-level role or group that produced it.
Q: How should teams design access requests so reviewers can assess them consistently?
A: Use a standard request structure with the same justification fields, ownership data, and entitlement naming across the programme.
Q: What happens when access reviews cannot show downstream assignments?
A: The review process certifies only part of the access picture, which leaves inherited permissions and subordinate entitlements outside the approval decision.
Practitioner guidance
- Standardise access request templates Define a single request structure for common entitlements so approvers see the same fields, justification, and ownership data across business units.
- Expose child entitlements in review workflows Make inherited and downstream assignments visible inside certification views so reviewers can approve the full effective access state, not only the top-level role.
- Govern the gateway deployment path Track the Cloud Application Gateway as a managed service asset, with explicit control over container image, configuration baseline, and upgrade ownership.
Bottom line: The release focuses on access request usability, review context, and deployment management rather than on new identity policy theory.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
25/06/2026 7:13 am
Reviewer visibility is now part of access governance, not just reporting hygiene. If a reviewer cannot see child assignment status, the certification process is blind to the actual entitlement being approved. That turns review from a control over access into a control over paperwork, which is a weaker governance state for any IAM programme.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: Should organisations treat gateway deployment choices as part of IAM governance?
A: Yes. When an integration gateway is part of the access control path, its deployment model affects repeatability, administration, and the risk of configuration drift. Governance teams should treat container image control, configuration baseline, and update ownership as part of the same operating model as the access workflow.
👉 Read our full editorial: Omada Identity Cloud April 2026 release sharpens access governance