Summary

The Policy Summary Page serves as a centralized view of individual policies. It provides a concise overview with key details that help users quickly understand the policy overview, its associated objects, related policies, and change log information.

Policy Curation

Policy curation plays a critical role in ensuring that organizational policies are consistent, relevant, enforceable, and aligned with business objectives and regulatory requirements.

Relating a policy to another policy means creating a logical link between two governance policies to establish hierarchy, dependency, or contextual relevance. It is beneficial in situations where multiple policies are interconnected, such as a data access policy that depends on a broader data privacy policy.

Example: Suppose you have a "Customer Data Access Policy" that governs who can access customer data fields in your organization. You may relate it to a broader "Data Privacy and Protection Policy," which outlines the general principles for handling personal data. By establishing this relation, you indicate that the access policy is governed by and must align with the overarching privacy policy. It helps in maintaining policy consistency and traceability.

Change Logs automatically track all modifications made to policies. These logs record the changes made, the individuals responsible, and the dates of occurrence. It provides a transparent audit trail for compliance and accountability.

• Users with governance roles can edit and refine the policy content.

• Policies can be linked to specific data assets.

Publish the Policy (Through Workflow) & Policy Status

Publishing policies by Governance roles is crucial because it ensures that policies are formally reviewed, approved, and communicated within an organisation’s governance framework. Note: Users with the Policy Creator or Governance roles can publish policies directly.

• Policies in Draft state must undergo approval before being published.

• Approval is managed through workflow automation.

• Status changes to Published after approval.

From the Summary page, users with Governance Role or Policy Creator access can directly trigger the workflow and publish the policy.

Users who don’t have access to publish the policy can click the ‘Request to Publish’ option to raise a service request to publish the policy.

Users can add a request description and click ‘Yes’ to trigger a service request. The request will be reviewed by the Policy Creator or Governance roles linked to the policy, who will then approve or reject it.

Policy Version

The policy version refers to the specific iteration of a policy document or configuration. Each time a policy is created, modified, or updated—whether due to changes in regulations, internal compliance requirements, or business processes—a new version is generated. This versioning enables organizations to maintain a clear audit trail, ensuring traceability and accountability for all changes made over time.

Versioning is automatic, starting with the initial version labeled as 0 (Draft). Once the policy is published, it becomes Version 1.

Note: Any updates made while in Draft mode do not increment the version number until the policy is republished. Users can update the policy version to their desired number themselves, and this doesn't increment the number later.

Governance Roles

Governance roles are essential for ensuring clear accountability, streamlined decision-making, and consistent policy enforcement across an organization. These roles define responsibilities such as policy creation, approval, monitoring, and auditing, which help maintain compliance with both internal standards and external regulations. By assigning specific roles, such as Steward, Owner, Custodian, and Governance Roles 4,5 & 6, organizations can mitigate risks associated with unauthorized changes, ensure that policies remain up-to-date, and foster transparency and traceability in governance activities.