A national digital account, with no centralised personal data.
Architecture d’entreprise pour un compte numérique national, privacy by design.
For the Digital Development Agency (ADD), I designed the national business space and structured the shared modules of the digital account: identity with the DGSN, roles and powers of attorney, a notification hub and a digital locker.
My roleEnterprise architect, freelance mission (2024)
ClientADD (Digital Development Agency)
ScopeIdentity · Business space · Notification · Digital locker
01 — THE CHALLENGE
Simplify the relationship with government, without a central file.
Law 55-19 requires procedures to be digitised and users to be notified. Companies must be able to deal with several administrations through managers and representatives who hold different roles.
The first, centralised version created a data-protection risk. The architecture had to be rethought so the platform manages authorisations without keeping any personal data, while staying simple for the user.
02 — THE APPROACH
Four architecture principles.
1Privacy by designData stays on the user’s device. The server keeps only anonymised identifiers and roles, in line with law 08-09.
2Rely on sources of authorityIdentity comes from the DGSN, and a company’s existence from the trade register: nothing is re-entered or duplicated.
3Shared modules, built onceIdentification, notification, the locker, signature and payment are designed once for every administration.
4Iterate with the decision-makersEach version is presented to e-Gov management, then adjusted in workshops: the mobile V2 came out of those exchanges.
03 — THE ARCHITECTURE
An identity foundation, and shared modules.
User and interfaceSource of authorityIdentity and authorisationsData protectionShared moduleGovernance and methodService delivered
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click a component
Click a component to see what it does.
Users and the mobile appThe manager and their representatives, with data kept locally and encrypted.
Identity and authorisationsSSO, strong DGSN authentication, roles, invitations, powers of attorney and the access log.
Shared modulesA multichannel notification hub, the digital locker, trust services and payment.
Service providersAdministration portals, which receive an authenticated user and their role.
04 — HOW IT RAN
Four phases across 2024.
1
Macro analysis and designReview of the existing estate, a benchmark of citizen and business accounts, and design of the shared identification modules and the business space.
2
MVP design and deliveryUser stories and acceptance criteria across about twenty workshops, screen design, a pivot to the mobile V2 with no central store, and weekly follow-up of development through to close.
3
Authentication journey with the DGSNWorkshops to integrate the digital-identity SDK directly, and BPMN modelling of the invitation and role-assignment journeys.
4
Notification hub and digital lockerAn international benchmark, functional scoping, Design Thinking workshops with the Digital Factory through to the story map, a gap analysis of an open-source solution, and a study of the digital locker.
05 — WHAT IT SHOWS
From strategic framing to a delivered MVP.
IS urbanisationIAM and SSODigital identityPrivacy by designBPMNDesign thinkingBenchmarkMultichannel notification
The personal data that is easiest to protect is the data you do not store.
This approach (sources of authority, shared modules, data protection from the design) transfers to any platform that manages identities, authorisations and exchanges between organisations.
CONTACT
A transformation programme to frame?
Identity, a shared platform or an information-system architecture: describe what you need in a few lines.
Anass Benouhoud