Governance rules
You create goverance rules to provide a natural-language description of the criteria that are used to determine whether data assets are compliant with business objectives. Governance rules are governance artifacts that you create within a category.
If you have the required permissions, you can create governance rules.
Required permissions To author a governance rule, you must have this user permission:
- Access governance artifacts
Additionally, you must have one of these category collaborator roles in the primary category for the governance rule:
- Admin
- Owner
- Editor
- A custom role with the permission to create governance rules.
The following description can give you deeper insights into:
Primary category
The primary category identifies the governance rule.
Secondary categories
Secondary categories can include governance rules, but do not control them. A governance rule can be referenced by one or more secondary categories other than its primary category. See Adding secondary categories.
Details
You can edit custom attributes on the governance rule that provide additional information.
Custom attributes can be created using the Watson Knowledge Catalog API. If any custom relationship
types are defined, they are also shown here. Inverse relationships show up in the other artifact after you publish the artifact where you created the relationship.
Not all Watson Knowledge Catalog plans provide the option to have custom relationships on governance rules.
Parent policies
You can assign the governance rule to parent policies.
Required permissions
You must have one of these category collaborator roles in the primary categories for both artifacts to add a relationship between them:
- Admin
- Owner
- Editor
- A custom role with the permission to edit both policies and governance rules.
For example, a policy named Software Security states that software security procedures must be in place, including virus-checking software. A governance rule named Virus-checking Procedures states that virus-checking software must be updated on each computer once a week. Therefore, the author of the rule Virus-checking Procedures specifies the policy Software Security as a referenced policy to the rule.
Related rules
You can assign the governance rule to related rules.
Required permissions
You must have one of these category collaborator roles in the primary categories for both artifacts to add a relationship between them:
- Admin
- Owner
- Editor
- A custom role with the permission to edit governance rules.
The relationship is symmetrical. If you specify that rule A is related to rule B, then rule B is related to rule A. A rule can have multiple related governance rules.
For example, you might create a rule named "valid address" that is related to another rule named "valid city name." Related rule relationships are bidirectional. For example, if you specify that the rule "valid address" is related to the rule "valid city name," then "valid city name" is automatically related to "valid address."
Related artifacts
You can assign the governance rule to:
-
Business terms
Select the business term to which you want to assign the governance rule. A governance rule can relate to multiple business terms.
For example, a governance rule can govern a database table. Terms can also be designated as governed assets. For example a rule named "ensure income meets minimum level" might govern a term called "income." -
Classifications
Select the classifications to which you want to assign the governance rule. A governance rule can relate to multiple classifications. -
Reference data
Select the reference data to which you want to assign the governance rule. A governance rule can relate to multiple data classes.
Required permissions
You must have one of these category collaborator roles in the primary categories for both artifacts to add a relationship between them:
- Admin
- Owner
- Editor
- A custom role with the permission to edit both artifact types.
Learn more
Parent topic: Governance rules