Overview
Governance & Compliance keeps a workspace’s management-system work in one place: the frameworks it works towards, the controls that meet their requirements, the evidence behind each control, the policies members must read, the risk register, internal and external audits with their findings, and the corrective and preventive actions that close them. Every readiness number is a Self-assessment: it counts how many of your mapped controls you have marked ready. It is not an audit opinion and it is not a statement by any standards body.Where to find it
The old HR policies page (
/hrms/policies) now redirects to /compliance/policies. Statutory HR
records (PF, ESI and similar) stay in HRMS under Compliance.
Core workflows
Adopt a framework
- Open Frameworks and pick a framework from the catalogue (for example ISO/IEC 27001, ISO 9001, SOC 2, GDPR or India’s DPDP Act).
- Choose Adopt and set its scope. Its requirements appear as a tree with the number of controls mapped to each one.
- A requirement marked Structure pending verification comes from a catalogue entry whose clause structure has not yet been checked against the published standard.
Run a control
- Open Controls, then create a control or edit one that a compliance pack added.
- Give it an owner and a reviewer, map it to framework requirements, and set its test cadence.
- A control counts as ready in the readiness view once its implementation and evidence say so.
Submit and approve evidence
- Add evidence to a control as a file or a link, then submit it.
- A member who holds the evidence approval permission approves or rejects it. The person who submitted the evidence can never approve it, and an AI agent can never approve evidence.
- A new upload creates a new version; the earlier versions stay on record.
Publish a policy and collect acknowledgements
- Draft a policy in Policies, then submit the version for approval.
- Once approved, the version is published. If it requires acknowledgement, every member in its
audience sees it in My policies (
/compliance/policies/my) and acknowledges it there. - The policy list shows how many members have acknowledged the current version.
Track risks, audits and actions
- Risks keeps the risk register with a 5 × 5 likelihood and impact matrix. Selecting a cell filters the register to the risks in it.
- Audits & Findings records each audit and the findings it raised.
- Actions holds the corrective and preventive actions for findings and risks. An action can be linked to a task so the work is tracked in Projects.
Permissions
Owners and admins see the whole module. Managers see frameworks, controls, evidence, risks, audits and actions across the workspace. Employees see the controls, evidence and actions they own and the policies addressed to them; their Overview shows only the policies waiting for their acknowledgement. Consultants see only the policies addressed to them. Clients do not see the module. The module opens with any one of these keys:
A workspace key covers the matching own key. Every department can view the module by default,
because every member must be able to read and acknowledge policies; HR, HR & Admin and Leadership
departments can manage it. Write power comes from role permissions, not from the department.
The module can be switched off in Settings → Modules. When it is off, it is hidden for every
member, owners included.
Known limitations
- AI systems inventory and regulatory obligations registers are not part of this module.
- Readiness is a self-assessment only. AmDital does not audit your controls or issue any attestation.