Plan capacity for centralised permission management against measured growth rather than optimism.
Designing Centralised User Permission Management Systems
A concise, decision-focused programme covering centralised permission management end to end.
📍 Tunis🗓️ 5 training days📚 4 modules🎓 Accredited certificate
5intensive training days
4scientific modules
8training sessions
32detailed points
Course Overview
Availability targets for centralised permission management are commercial commitments, whatever the engineering team calls them. Systems supporting this aspect of technology and systems delivery fail in ways that are obvious afterwards and invisible before. Field experience suggests that the barrier to better the technology and systems delivery capability is rarely technical. It treats centralised permission management as an operating discipline and equips participants to run it as one. Each session closes with a decision the participant must justify about the wider technology and systems delivery agenda in their own setting. Participants gain a clear basis for measuring what this strand of technology and systems delivery has actually achieved. Ambition around centralised permission management outruns capacity unless the sequencing is deliberate. The programme works equally well for those formalising the wider technology and systems delivery agenda for the first time and those improving an existing approach. The course ends by identifying what the participant will stop doing to make this strand of technology and systems delivery sustainable.
Expected Learning Outcomes
Apply a repeatable review cycle to centralised permission management and act on what it produces.
Test the organisation's response to centralised permission management under conditions that are less than ideal.
Measure delivery and reliability of centralised permission management with indicators teams trust.
Communicate the purpose of centralised permission management to those who have to comply with it.
Apply data protection and retention requirements within centralised permission management.
Build the deployment pipeline for centralised permission management so releases are routine rather than events.
Who Should Attend
Newly appointed managers taking on centralised permission management for the first time.
IT governance and audit staff reviewing centralised permission management.
Analysts producing the data on which decisions about centralised permission management rest.
Project managers delivering changes to centralised permission management.
IT managers and service owners responsible for centralised permission management.
Software engineers and technical leads building centralised permission management.
Course Modules
Centralised permission management: architecture and designing for failure
2 sessions · 8 pointsSession 1The hard cases in centralised permission management and how to reason about them
- Benchmark the organisation's centralised permission management against comparable operations.
- Set delivery and reliability indicators for centralised permission management the team trusts.
- Confirm that contractual obligations around centralised permission management are understood.
- Agree the smallest change to centralised permission management that would be visibly useful.
Session 2The change to centralised permission management that caused the last outage
- Rehearse the briefing on centralised permission management that would follow an incident.
- Distinguish symptoms from causes when centralised permission management underperforms.
- State the availability and recovery objectives for centralised permission management as numbers.
- Confirm every release of centralised permission management can be rolled back within a defined time.
Centralised permission management: security, identity and least privilege
2 sessions · 8 pointsSession 1The decisions in centralised permission management that cannot be delegated
- Anticipate the objections centralised permission management will raise and prepare the answers.
- Assess the exit route from any cloud or vendor dependency in centralised permission management.
- Define acceptance criteria for centralised permission management in advance.
- Establish who is informed, consulted and accountable in centralised permission management.
Session 2Sizing capacity for centralised permission management on measured growth
- Confirm the support model and escalation path for centralised permission management.
- Restore a backup of centralised permission management in a test environment and time it.
- Configure alerting on centralised permission management that reflects what users experience.
- Measure current load on centralised permission management and project it forward twelve months.
Centralised permission management: backup, recovery and continuity
2 sessions · 8 pointsSession 1Proving the backup of centralised permission management by restoring it
- Review access rights on centralised permission management and remove what is no longer needed.
- Agree what will be standardised in centralised permission management and what will not.
- Record the technical debt in centralised permission management and schedule repayment.
- Confirm data retention and deletion rules applied within centralised permission management.
Session 2Where centralised permission management typically breaks, and why
- Plan the sequence in which improvements to centralised permission management will be introduced.
- Define incident severity levels for centralised permission management and the response each triggers.
- Establish what evidence demonstrates centralised permission management is under control.
- Inventory third-party dependencies inside centralised permission management and their update status.
Centralised permission management: build, pipeline and release discipline
2 sessions · 8 pointsSession 1Setting availability and recovery targets for centralised permission management honestly
- Estimate the resource centralised permission management requires to run as designed.
- Apply change control to centralised permission management including emergency changes.
- Document the runbook for centralised permission management to the level a new engineer could use.
- Close out actions on centralised permission management rather than leaving them open indefinitely.
Session 2Monitoring centralised permission management from the user's point of view
- Test the failover for centralised permission management rather than assuming it works.
- Build the internal briefing that explains centralised permission management to those affected.
- Map the handovers in centralised permission management between functions and secure them.
- Agree the indicators that will show whether centralised permission management is improving.
Choose the package that suits you
Silver Package
At least 3 people
USD1,250
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Gold Package
At least 3 people
USD1,850
- 5-night stay in a 5-star hotel
- Workshop or Program Participation
- Airport Transfers
- Customized Badge
- Expert Mentorship (Private Sessions)
- Supervision & Secretarial Services
- Accredited Certificate of Participation
- Complete Training Kit
- Coffee Break
- Closing Ceremony
Complete your registration
We will contact you within one business day to confirm.