People and accountability
Every AI system has someone to call. CognaOne keeps a people register apart from console logins, so owners who never sign in can still be named, and leavers are handled cleanly.
Roles on an AI system#
| Role | How many | What it means |
|---|---|---|
| Business owner | One at a time | Owns the system day to day and answers for how it is used |
| Accountable executive | One at a time | The escalation line; for FAR entities, traceable to the accountable person for that key function |
| Reviewer | Any number | Second-line or specialist reviewers who check the system and its changes |
Each role has an effective date. When an owner changes, the old assignment is ended, not overwritten, so you can always say who was accountable on a given day.
The people register#
- Person: name, job title, optional email, function and business unit.
- Functions: a standard set of organisational functions, which you can extend.
- Business units: your own structure, never deleted, only made inactive.
- Link to a login: a person can be linked to a console user. Linked, never merged: the person record stays even if the login goes.
- Archive: a person who still holds a current role cannot be archived until the role is handed over.
The Financial Accountability Regime#
Roles on an AI system are CognaOne roles, not FAR status. FAR accountable persons and their responsibilities belong to the person and the entity, so they sit on the person record. The accountable executive on a system links to that person, and the AI accountability map follows the one you already maintain. See Financial Accountability Regime.
Last reviewed October 2026Suggest a change