Your roles do not survive the migration.
Twenty819 does one thing: we make sure authorizations hold when a landscape moves to S/4HANA. Role redesign, SoD remediation, Fiori authorization, audit readiness.
A specialist practice, not a bench.
Most system integrators staff security late and generically. We get called in by programme managers who have already watched that go badly once.
One discipline
Authorizations and SAP security. We don't sell you a functional stream you didn't ask for.
Senior only
Small team, no pyramid, nobody learning the object model on your landscape.
One owner
A named person is accountable for the workstream from blueprint through hypercare.
Services
Take one, or hand us the whole authorization workstream.
Role redesign
Business role catalogues built from usage data
SoD remediation
Conflicts ranked, mitigated and signed off
Fiori authorization
Spaces, pages and catalogues mapped to roles
Audit readiness
Evidence prepared before the auditor asks
SAP BTP security
IAS, IPS, role collections and API access
Baseline assessment
A fixed-price read of where you stand today
Why now
The dates that set the shape of every S/4HANA security plan.
ECC mainstream maintenance
Ends 31 December
Access surface after Fiori
Backend plus launchpad content
Phases in the workstream
Each ends in a written deliverable
Why the work belongs in 2026
The object model changed and controls need rewriting
Our approach
Four phases, four deliverables. You can join at any phase and stop after any phase.
Read the landscape
Usage data, role quality, SoD exposure, Fiori readiness
Design the catalogue
Business roles, derived structure, org levels, naming
Build and test
Build, positive and negative testing, defect turnaround
Hand over
Support model, recertification, emergency access
Bring us in at the gate that suits you.
Phase 01 stands alone as a fixed-price baseline assessment if you want to understand your exposure before committing a workstream.