Centralised management of a network of embassies and consulates
A foreign ministry does not run one mission but a network. The requirement looks contradictory: each post must work on its own data alone, and the ministry must be able to read the whole network.
Separation by mission
Each mission has its own space: its register, its cases, its officers. A post does not see another post's files, which is as much a data protection requirement as a condition for posts to adopt the system at all.
The separation extends to the address: each mission has its own subdomain, and the nationals' portals are distinct.
Each mission keeps its own branding
A mission applies its own colours and identity without a dedicated build. Personalisation is data, not a code variant: there is only ever one piece of software to maintain, fix and upgrade.
That is what separates a multi-mission platform from software deployed N times. In the latter case, the thirtieth mission deployed means thirty versions to evolve in parallel.
Consolidation at ministry level
Above the posts, the ministry reads the network: nationals enrolled per country, credentials issued, cases in progress, collections. Consolidation requires no manual reporting from the posts, which is the first thing to disappear when a post is short-staffed.
Mission-by-mission rollout
Bringing a whole network live at once is neither realistic nor desirable. Rollout goes post by post: the first mission acts as pilot, its feedback corrects the configuration, later ones benefit.
Each post keeps its own pace for data migration and officer training, without holding up the others.
Roles and permissions
Officers do not all hold the same rights: reviewing a case, approving a card, collecting a payment and reading statistics are distinct acts. Actions are logged and attributed to a named officer, as any after-the-fact audit requires.
Frequently asked questions
Can one post see another post's cases?
No. Data is separated per mission, down to the subdomain through which nationals reach their portal. Only ministry-level consolidation reads above the posts.
Does each mission get its own build?
No, and that matters: personalisation — colours, identity, document catalogue, prices — is data. There is only one piece of software to maintain, however many missions there are.
Does the whole network have to go live at once?
No. Rollout goes post by post, starting from a pilot mission whose feedback corrects the configuration before extension.
Are officer actions traced?
Yes. Acts are logged and attributed to a named officer, which makes it possible to retrace who approved what and when.