Obligations and requirements: The Frameworks and Controls screens use the word obligations for the individual rules a framework decomposes into. You may see the same idea called "requirements" in older material; they mean the same thing.

Go to the admin sidebar → Compliance → Frameworks. The page header explains the core idea: activate frameworks to link their obligations to your control register; controls are shared, so additional frameworks rarely increase your total workload.

Four tabs run across the top:

Each tab shows a live count, so you don't need to memorise how many of anything you have.

Frameworks are grouped by jurisdiction. You typically see an International group (ISO 45003) alongside jurisdiction groups (Australia, Canada, New Zealand, Singapore, and the United Kingdom) covering the relevant Commonwealth, state, and national codes. Each row shows the framework name, its short code, and your progress toward the target compliance date.

For the full list of what you can activate today, see Available frameworks (by jurisdiction).

Each control in the library maps to one or more obligations, and each obligation maps to one or more frameworks. So when you complete the evidence for a single control, that completion satisfies the relevant obligation across every framework that references it. A single control can carry many frameworks at once; the control's detail page shows a Frameworks badge with the count.

This is why multinational and multi-state organisations can activate several jurisdictions without multiplying their work. See Working with multiple frameworks.

Each framework can define roles that you map to people in your organisation (for example Compliance Officer, HSR, or Department Lead). The number on the Roles tab is the count of roles defined across all your frameworks combined.

For assigning your organisation's own application roles, see the "User roles and permissions" article in Getting Started.