OpenText NetIQ Identity Governance resources: Where to start and what to use
A guide to access reviews, business roles, policy-driven governance, and verified changes using OpenText and Micro Focus resources.

Buying an identity governance solution is a beginning, not a finished program. The real work is making access information trustworthy, getting the right people involved, responding to changes, and confirming that approved decisions actually take effect.
The first two articles in this series explored how to turn governance capabilities into business value and followed Sarah as she moved from finance to operations. This resource guide picks up there: where do you go when you want to improve your own processes?
OpenText™ NetIQ™ Identity Governance has practical guidance spread across OpenText Community articles and the Micro Focus documentation library. Here is a path through those resources, organized by the problem you want to solve.
1. Find your governance starting point
Before changing configurations, understand where the program is weak. Can application owners explain their permissions? Do reviewers have enough context to make decisions? Can your team demonstrate that a revoked entitlement is really gone? Those are better starting questions than how many certifications you completed last quarter.
A three-part OpenText Community series provides a useful progression: assess your capabilities, identify the gaps, and apply NetIQ governance practices to close them. Start with a few measurable weaknesses rather than launching an enterprise-wide redesign.
Resources: Assessing your access governance capabilities · Addressing your governance gaps · Leveraging NetIQ for identity governance gaps
2. Get the access data into shape
Good reviews start with good data. Collectors bring identity, account, and permission information from connected sources into the governance catalog. But collecting a code such as “FIN_AP_03” does not tell a business manager what that permission does.
Use the collector documentation to understand the available sources and mappings. Then work with application owners to improve descriptions and catalog attributes. Prioritize high-risk applications and permissions that reviewers repeatedly struggle to interpret.
Resources: Understanding collectors · Editing catalog attribute values
3. Design reviews people can complete intelligently
An access review is useful only when the right person can make an informed judgment. Review definitions determine scope and ownership; clear permission descriptions and business context help reduce routine approvals made without serious consideration.
The review documentation explains how to set up and run campaigns. Pair it with the Community article on access mistakes to see why reviewer context matters just as much as automation. Start by improving one frequently confusing review, then learn from the questions it generates.
Resources: Creating and modifying review definitions · Closing the door on access mistakes
4. Respond to changes between scheduled campaigns
Remember Sarah’s transfer? Waiting until the next quarterly certification might leave her old finance access in place for weeks. With appropriate data sources and configuration, Identity Governance data policies can detect relevant changes and initiate focused follow-up actions.
Use the data-policy guidance to define what deserves attention, and the certification guidance to decide how reviews should be governed. A change to an HR record is not, by itself, proof that access has been reviewed or removed. The collection, publication, review, and fulfillment process still matters.
Resources: Creating and managing data policies · Understanding certification policies
5. Make routine access easier with roles
A role model can reduce the time spent reconsidering access that is already well understood. Business roles identify people who share a business function and expected access. Technical roles organize permissions into manageable sets. Both require ownership, maintenance, and a clear understanding of exceptions.
The documentation covers defining business roles and technical roles, including how to build role structures without hiding access that deserves an individual decision. For an employee transfer, the objective is to simplify access for the new job without automatically carrying every old entitlement forward.
Resources: Creating and defining business roles · Creating and defining technical roles
6. Put risk and conflicting access in view
Some permissions should not be held together, even if each one is legitimate on its own. Separation of duties (SoD) policies help identify combinations that need review, while risk scoring can give teams another way to prioritize attention.
The SoD and risk guides are most useful when read with business policy owners. Technical rules should reflect actual financial controls, sensitive operations, and approval responsibilities—not simply produce another queue of alerts. Start with conflicts your organization can explain and resolve.
Resources: Separation of duties policies · Calculating and customizing risk
7. Close the loop on access decisions
A reviewer’s decision to remove access is not the same as removal. Depending on the integration, a fulfillment task may go to an automated system or a person. The important next step is checking the application data after the change.
The fulfillment guidance explains the process, while the status documentation distinguishes completed requests from verified changes and shows how to investigate errors or timeouts. That distinction is central to both earlier blogs: business value depends on follow-through you can demonstrate.
Resources: Understanding the fulfillment process · Monitoring fulfillment status
8. Measure progress and keep learning
A mature governance program improves between audits. Useful questions include which applications are still missing, where requests stall, which reviews take the longest, and how often revocations fail verification. Custom metrics and reporting can help turn those questions into operational priorities.
For a real-world compliance example, read how a defense contractor addressed access review and audit challenges. Then visit the Identity Governance community and release documentation when you are ready to expand coverage or reassess your practices.
Resources: Creating custom metrics · DoD contractor customer story · Identity Governance community · What’s new in Identity Governance 25.4
9. Turn the resources into your next improvement
You do not need to tackle every capability at once. Choose one issue—unclear access descriptions, missed transfer reviews, an inconsistent role model, or slow fulfillment—and use the corresponding material to improve it. Measure what changes, involve the business owners who can make decisions, and then move to the next gap.
The complete Identity Governance documentation library is available when you need implementation detail. For a broader framework on turning those capabilities into results, read Getting the most out of OpenText NetIQ Identity Governance.
Resources: Identity Governance Information Hub · OpenText NetIQ Identity Governance product overview




