-
Notifications
You must be signed in to change notification settings - Fork 2
Specs M1 Context Role
context.models.role.Role
Represents a role within the GRC framework.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto-generated | Unique identifier |
scope_id |
relation | FK → Scope, required | Linked scope |
name |
string | required, max 255 | Role title |
description |
text | optional | Role description |
type |
enum | required |
governance, operational, support, control
|
responsibilities |
relation | O2M → Responsibility | Associated responsibilities |
assigned_users |
relation | M2M → User | Assigned users |
is_mandatory |
boolean | required, default false | Mandatory role (required by a standard) |
source_standard |
string | optional | Source standard (e.g. "ISO 27001 - §5.3") |
status |
enum | required |
active, inactive
|
created_by |
relation | FK → User | Creator |
created_at |
datetime | auto | Creation date |
updated_at |
datetime | auto | Last modification date |
Responsibilities are managed directly from the role detail page:
adding, editing and deleting them through an HTMX drawer, with the section
refreshing without a full page reload. These actions are protected by the
context.role.update permission.
Any creation, modification or deletion of a responsibility sends the role
back to its initial state (draft): the approval is reset, the version is
incremented and the demotion is recorded in the role's history, so that it can
be re-validated. This behavior applies both from the interface and through the
REST API (Role.send_back_to_draft(), single source). Roles in a terminal
state (archived / cancelled) are not affected.
The role's history merges the history of its responsibilities (each
responsibility has its own HistoricalRecords tracking): adding, modifying and
deleting a responsibility therefore appear on the role's timeline. A deletion
displays the values of the removed responsibility and carries a "Responsibility"
label.
Sub-entity: responsibility associated with a role.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto-generated | Unique identifier |
role_id |
relation | FK → Role, required | Parent role |
description |
text | required | Responsibility description |
raci_type |
enum | required |
responsible, accountable, consulted, informed
|
related_activity_id |
relation | FK → Activity, optional | Associated activity |
created_at |
datetime | auto | Creation date |
updated_at |
datetime | auto | Last modification date |
Built from docs/ at v0.36.0. Edits made here are overwritten by the next release : open a pull request against the source instead.
- Administration
- Ask Cairn
- Assets and suppliers
- Compliance
- The dashboard
- Finding your way
- Getting started
- Incidents
- How records move
- Organisational context
- Reports and management review
- Risks
- Trust Center
- Architecture
- Configuration
- Contributing
- The documentation system
- Installation
- Internationalisation
- Operations
- Release process
- Security
- Testing
- Adding an assistant provider
- Adding a dashboard widget
- Adding a domain entity
- Declaring a lifecycle
- Adding an MCP tool
- Adding a REST endpoint
- Adding a report
- Interface conventions
- Dashboard widgets
- Lifecycles
- MCP tools
- MCP tool parameters : Assets
- MCP tool parameters : Compliance
- MCP tool parameters : Governance and context
- MCP tool parameters : General
- MCP tool parameters : Incidents
- MCP tool parameters : Reports and management review
- MCP tool parameters : Risks
- MCP tool parameters : System and administration
- MCP tool parameters : Trust Center
- Management commands
- Models
- Permissions
- REST endpoints
- Environment variables
- MCP server
- REST API
- Assistant module (Ask Cairn)
- Module 0: User Management and Access Control
- Module 1: Context and Organization
- Module 2: Asset Management
- Module 3: Compliance
- Module 4: Risk Management
- Module 4 bis - EBIOS Risk Manager
- Module 5 : Trust Center
- Module 6 : Security Incident Management
- Management review : ISO 27001:2022 compliance (clause 9.3)