Learning & compliance
An obligation with a person against it.
A governance requirement that names a department is a requirement nobody owns. Connecting the register to the People Graph resolves each one to a named person with a backup.
What connects
A connection that maps governance obligations to responsibilities here, so each control has a current owner rather than a role description.
What crosses the boundary
- Received: obligations, their frequency and their required evidence.
- Sent: the current owner and backup for each mapped responsibility.
- Sent: evidence that a responsibility was discharged, where it exists here.
- Received: changes to obligations, which flag the responsibilities affected.
What this lets you do
- Resolve every control to a named person rather than a function.
- Flag obligations whose owner has left or changed role.
- Supply discharge evidence from the responsibility record.
- Show which obligations currently have no backup.
Setting it up
- 1Link the workspaces.
- 2Map obligations to responsibilities one at a time — bulk mapping produces wrong owners.
- 3Review obligations with no mapping, which is the useful gap list.
- 4Set who is notified when a mapped owner changes.
Permissions
Scoped to obligations and the responsibilities you map to them. No personal data beyond the owner's name and role crosses the boundary.
What you can ask once this is connected
- “Which obligations have no named owner?”
- “Who owns this control now that Laura has left?”
- “Show obligations whose owner changed this quarter.”
Where it stops
Orglume supplies the people half. It does not assess whether your controls are adequate, interpret regulation, or determine what your obligations are — that work belongs in the governance product and with your advisers.
Run your team with clarity.
From the moment someone joins to the day their responsibilities are handed over, Orglume keeps your people, their work and your organization connected.
Set up from a spreadsheet · Nothing about the AI is metered · [email protected]