Notifications
Clear all
Topic starter
27/06/2026 1:29 pm
TL;DR: A fully configurable homepage and role-based landing page assignment in Collibra’s 2026.06 release let administrators route users to different entry points, with Gartner cited as saying role-based UX can improve time-to-value by up to 30%. The governance implication is that landing-page logic is now part of adoption, access design, and operational context, not just UI polish.
NHIMG editorial — what this means for NHI practitioners
Questions worth separating out
Q: How should organisations use role-based homepages in governance platforms?
A: Use them to reduce friction between a user's role and the work they need to do first.
Q: When does a customizable homepage become a governance risk?
A: It becomes a risk when landing-page rules are unmanaged, unclear, or inconsistent with current role design.
Q: What should IAM and IGA teams look for in role-based UX changes?
A: They should look for whether the change improves first-use efficiency without creating hidden entitlement complexity.
Practitioner guidance
- Map homepage defaults to personas and roles Define which user groups should land on the governance homepage, the Data Marketplace, or an onboarding view, then document the rule order so first-match precedence is deliberate.
- Treat homepage changes as governed releases Use draft and preview before publish, and keep a rollback path ready so a layout change does not disrupt users who rely on the homepage for daily workflows.
- Review landing-page rules alongside access reviews Check whether the default entry point still matches each role's actual operating needs, especially after reorganisations, new programmes, or role changes.
What's in the full announcement
Collibra's full blog post covers the operational detail this post intentionally leaves for the source:
- Step-by-step configuration of landing-page rules in Settings > General > Landing Page
- Widget-level layout options, including counters, tasks, search bars, and embedded views
- Default landing page selection for unmatched users and the rule precedence model
- Draft, preview, publish, and restore workflow details for admins managing the homepage
👉 Read Collibra's post on customizable homepage experience and role-based landing pages →
Collibra homepage personalization: what it means for IAM teams?
Explore further
27/06/2026 2:50 pm
Homepage design has become a governance control point, not a presentation layer. When a platform's first screen determines whether users reach tasks, scorecards, or search, the landing page influences how identity, access, and workflow are experienced in practice. That makes entry-point control part of programme design, especially where role-based adoption matters across data stewardship, analytics, and executive oversight. Practitioners should treat homepage routing as a governed control surface.
A few things that frame the scale:
- The average organisation believes more than 1 in 5 of their non-human identities are insufficiently secured, according to The 2024 ESG Report: Managing Non-Human Identities.
- 72% of organisations have experienced or suspect they have experienced a breach of non-human identities, with 46% confirmed and 26% suspected, according to The 2024 ESG Report: Managing Non-Human Identities.
A question worth separating out:
Q: How do you govern default entry points without creating confusion?
A: Use explicit rule ordering, limit overlap, and define one default path for unmatched users. Then review those rules whenever organisational roles, onboarding paths, or governance priorities change. Clear precedence matters because users experience the first matching rule, not the one that seems most intuitive after the fact.
👉 Read our full editorial: Collibra homepage customization and role-based landing page control
