Information patterns
IT pattern A – Applications and access rights
Shows where an access right comes from and where it lands: the person holds one or more engagements as an employee, placed in a unit, and each engagement gets its own digital identity. The process role gives the function – what may be done in the application. The role's link to a unit (scope, by default the own unit and inherited down the tree) gives the information – which data the access right covers. The right is then provisioned to the digital identity. The identity states who, the process role what and the unit where; access is never granted directly to the person or based on title.
Pattern diagram
A data-driven diagram of information building blocks and their relationships.
Pattern ownership
Patterns always arise as a whole in the organisation's processes. The governing process decides that the pattern is the standard; the instantiating processes create, change and end its nodes and relationships.
- Governing process (owner)
- Govern information management and architecture
- Instantiating processes
- Manage digital identityManage application assignment
The whole model is owned by the process Govern information management and architecture with a mandate from top management – never by a single function such as HR, finance or IT.
Business rules that apply to this pattern
- Permissions are granted via process roleVR-PRC-009 · Responsibility rule
- Process roles can be reused across multiple processesVR-PRC-014 · Cardinality rule
- Digital identity per engagement and organisationVR-IT-001 · Uniqueness rule
- The identity follows the engagement's validityVR-IT-002 · Conditional rule
- Access rights are granted to accountsVR-IT-003 · Responsibility rule
- The committee is a confidentiality boundary for access rightsVR-IT-005 · Conditional rule
- The application is managed by a unitVR-IT-006 · Responsibility rule
- Tool needs are separate from access rightsVR-IT-009 · Responsibility rule
- Application assignment is verified annuallyVR-IT-011 · Responsibility rule
- Accounts always have an owner with an active engagementVR-IT-012 · Cardinality rule
- Accounts are never shared between peopleVR-IT-013 · Uniqueness rule
- Absence pauses administrative accounts but not personal onesVR-IT-014 · Conditional rule