Configuring security for Governance console

Governance console uses a role-based security model to provide a way for administrators to control user and group access to objects. By assigning a role to a user or group at a specific security context point in the object hierarchy, you can control access to objects. Roles represent the usual or expected function that a user or group plays within an organization. Some examples of roles are: Finance Reviewer, Tester, External Auditor, System Administrator, Control Owner, Risk Assessor.

For more information, see Role-based security model.

Security rules provide an extra level of security that works with role-based security. You define security rules for individual object types. After you define them, the rules are applied to all system components, including Reporting, FastMap, Triggers, Reporting Periods, and all available views.

You can create two levels of security by using security rules:

• Record level security allows administrators to control access to individual objects in a folder.
• Field level security allows administrators to control access to individual fields within an object.

For more information about security rules, see Security rules.

Assigning profiles

Assign user profiles to your business users based on their set of governance goals. For example, if the user needs administrative access to the object types for model risk governance to provide them with insight into business processes and regulations, assign them the watsonx.governance MRG Master profile.

A profile provides users with a view of information that is directly related to their responsibilities. It gives users and groups access to object types, fields, and views. When you change a setting in a profile, the change is dynamic and the change is immediate.

For more information about profiles, including descriptions of the predefined profiles, see Solution components in Governance console.

Defining dashboards for profiles

Define dashboards in the UI that apply to specific profiles so that users see a default dashboard based on the profile that they belong to. Users can still customize their dashboard by adding their own dashboard panels or hiding default dashboard panels.

For more information, see Defining a dashboard for a profile.

Configuring views

Configure views to control what information is displayed to users and to determine how users interact with Governance console. You design the content and layout of a view by using the View Designer.

For more information about configuring views, see Views and Using the View Designer.

Enabling questionnaires

To enable users to answer questionnaires, set up access to object types for users, configure the email server, and customize the landing page. For more information, see Getting started with questionnaire assessments.

You can create or edit questionnaires, and you can set up questions in a questionnaire so that they perform specific actions based on the answers. For example, you can configure a response action that creates or copies objects, or sets the value of fields on objects.

For more information, see Questionnaire templates.

Enabling tags

Enable the tagging feature and create tags that business users can apply to objects in Governance console to categorize them. When tags are applied to objects, business users can use a search to find objects that belong to a specific category.

For more information, see Creating tags.

Viewing workflows

Each solution includes workflows. A workflow represents a business process and describes the tasks that are involved in the process. A workflow is defined for one object type. An object type can have multiple workflows. For example, the Model object has a Model Validation workflow and Model Deployment workflow. The two workflows reflect two different business processes for Models.

To view a list of workflows, click > Solution Configuration > Workflows.

To design and create workflows, see Configuring GRC Workflow.

Configuring calculations

Configure calculations to automatically set values on fields. For example, a calculation can set a field when one of the following events occurs:

• An object is created.
• Calculation input fields are updated.
• Object associations are made.
• A workflow action starts that runs a calculation.

For more information, see Setting up GRC Calculations.