Stakeholder Role Access Control Policy in Informatica Cloud Data Governance & Catalog (CDGC)

Stakeholder Role Policies in Informatica Cloud Data Governance

Introduction to Stakeholder Role Policies

• This video is the second part of a series discussing stakeholder role policies in Informatica Cloud Data Governance and Catalog (CDGC) after covering access control policies and user roles in the first part.

• Viewers are encouraged to watch the previous video for foundational knowledge before proceeding with this content.

Understanding User Role vs. Stakeholder Role Policies

• User role policies can grant access to asset types for groups of users, but individual asset access requires stakeholder role policies. For instance, a user role policy may allow all glossary stewards to manage business terms, while specific stakeholders can be assigned for individual terms.

• If no stakeholder is assigned to an asset, its access defaults to the user role or group policy associated with that asset type. When stakeholders are designated, non-stakeholders retain read-only access based on their respective user role policies.

Effective Permissions Calculation

• The effective permissions for a user added as a stakeholder depend on multiple factors:

• Read/edit/delete permissions from user role policy.

• Read/edit permissions from stakeholder policy.

• Read permissions from non-stakeholder policy.

This layered approach determines what actions a stakeholder can perform on an asset.

Demonstration of Access Control

• A demonstration involves creating two glossary steward users within IDMC Administrator and assigning them custom roles that provide comprehensive access rights across business terms. Both users can view and edit these terms as well as assign stakeholders.

• To restrict updates on specific assets (e.g., "customer contact"), one glossary steward must be assigned as a stakeholder while another only retains read access by modifying their roles accordingly. This ensures controlled management over sensitive data assets.

Creating and Assigning Stakeholder Roles

• Steps include designating custom user roles as stakeholder roles at the business asset level, followed by creating corresponding stakeholder policies that define which actions (create, delete, manage) are permitted for those assets selected under this new policy framework.

Edit and Manage Access Permissions in Business Terms

Overview of User Permissions

• The edit permit is no longer available for a user when checking business terms that have stakeholders.

• In cases where there are no stakeholders, the user retains edit and manage access permissions.

• The example provided involves an "amount" business term, which lacks a stakeholder, allowing options to add or edit stakeholders.

Glossary Steward User Capabilities

• A glossary steward user can log in and view all business terms.

• When checking the customer contact term, it is noted that this user has been added as a stakeholder.