Library · Travel & housing – master data in detail

DAT-110 · Assign roles and permissions in the travel/housing system

Implements the library's access matrix technically, so data minimization doesn't depend on discipline but on permissions — and revokes rights again…

Travel & housing · master data

Overview

Who it's for

Coordination, assistance, office

Trigger

Person gets system access for the first time, changes role, or the recertification deadline {{RECHTE_REZERTIFIZIERUNG_TAGE}} is reached.

You get

Implements the library's access matrix technically, so data minimization doesn't depend on discipline but on permissions — and revokes rights again once the role ends.

Status: Concept – not built yet

Implements the library's access matrix technically, so data minimization doesn't depend on discipline but on permissions — and revokes rights again once the role ends.

Trigger: Person gets system access for the first time, changes role, or the recertification deadline {{RECHTE_REZERTIFIZIERUNG_TAGE}} is reached.

1Derive rightsprofile from role2Justify andapprovedeviations fromthe standardPL3Limit rights tothe contractperiod4Grant access to`VAULT` only withproven necessityDSB5Log the grant andrecord it in theprocessingregister6Triggerrecertificationon a cycle andrevoke7Fully revoke oldrights on rolechange before newones apply

Rule (automatable) Judgment (human decides)

Decision rules

  • R1 IF role is known THEN assign standard profile per matrix 3.2; individual rights outside a profile are not granted.
  • R2 IF access to VAULT (D4, D5) is requested THEN justify the necessity in writing and involve DSB; no access without justification.
  • R3 IF the contract period ends THEN revoke rights automatically at the end of the last contract day, regardless of whether DAT-130 has already run.
  • R4 IF a role change occurs THEN revoke first, then grant; accumulation of rights across multiple roles is not allowed.
  • R5 IF recertification after {{RECHTE_REZERTIFIZIERUNG_TAGE}} is not confirmed by PL THEN revoke rights automatically and inform the person.
  • R6 IF an external role (HOT, RDL, TXI, STB) needs access THEN only after a completed DPA (CMP-090) and only to the minimum data set.

Common pitfalls

1. Production assistant gets full access for a single task that's never revoked → permanent access to passport data and guest terms. 2. Rights of a departed person stay active because offboarding depends on contract renewal → access after project end. 3. Approvals are shared as a list screenshot in group chats because system access is missing → bypassing the rights matrix despite a formally correct rights setup. 4. Two roles at once (dispatch and driving service management in a small team) → combined rights beyond what's required.

Impact H × Effort S → Do-first · HITL · RACI **R** ITA · **A** PL · **C** DSB, THK · **I** HL · Manual effort: Estimate: 5 min. per assignment using a profile; 20–30 min. per VAULT request with justification and review

Request this workflow

Request this workflow See all workflows