Authorized Registration

Service documentation · Republic of Zambia · GSB e-Services

Owner	Cadastre Department
Service key	MMMD/authorized-registration
Version	service v1, platform a0a302b8
Date	2026-10-21

Generated automatically by the service's end-to-end test run. Every screenshot shows synthetic test data on a local test installation, never real personal data.

This document describes the Authorized Registration service of Cadastre Department as the platform runs it today. It is generated by the service's end-to-end test: every step below was performed by the test, and every screenshot was taken during that run with synthetic data. Regenerate it with npm run docs:services in the e2e suite; do not edit it by hand.

1. Service summary

Item	Detail
Service	Authorized Registration
Owner (MDA)	Cadastre Department (MMMD)
Purpose	This allows users to apply for access to a corporate account using a letter from the corporation granting them power of attorney.
Who can apply	Not set in the service configuration.
How to apply	Online on the national e-Services portal, signed in with ZamPass; pay with ZamPay.
Fees	Free of charge: ZMW 0.00
Turnaround	N/A
Validity of the output	N/A
Required documents	None
Output documents	GS-1 Application for a Government Service GS-2 Notice of Government Action

2. Application process, step by step

The process as configured in the back office:

Step	Role	Task	Type
1	Applicant	Apply	form
2	System	Generate Document	generate-document
3	Case Officer	Approve	approve
4	System	Generate Document	generate-document
5	System	Notify Client	notify

Who takes part in this journey: Citizen, Case Officer, Anyone (public).

Step 1. Find the service

Citizen · National e-Services portal

On the national e-Services portal the citizen opens All Services and searches for the service by name ("Authorized Registration"). Each result names the service and the ministry that provides it.

Step 2. Read the service page

Citizen · National e-Services portal

The service page sets out what the service is for, who provides it, the fee, how long it takes and the documents to have ready. "Start application" begins an application (the citizen is signed in with ZamPass).

Step 3. Confirm the applicant details

Citizen · National e-Services portal

The applicant details are filled in from the citizen's ZamPass account. The citizen says whom they are applying for (themself) and continues with "Proceed to Application".

Step 4. Fill in the application form

Citizen · National e-Services portal

The citizen answers the service's own application form, converted from the legacy system (8 answers in this run, all synthetic), for the type of application "New". Questions marked * must be answered; some appear only after an earlier answer. Answers are saved as the citizen types, so an unfinished application can be reopened from My Workplace.

Step 5. Upload the supporting documents

Citizen · National e-Services portal

The service asks for no supporting documents, so the citizen continues straight to the check of the answers.

Step 6. Check the answers and confirm the declaration

Citizen · National e-Services portal

Before sending, the citizen sees every answer and document on one page and can go back to change them. The declaration that the information is true and complete must be ticked.

Step 7. Application sent

Citizen · National e-Services portal

The portal confirms the application with the ministry's reference number (MMMD-AR/00001/10-21-26 in this run). The application goes to the ministry's officers; the citizen follows it in My Workplace.

Step 8. Take the new application on

Case Officer · Back office

The application arrives in the case queue of the ministry that owns the service (Cadastre Department); only its staff see it. The officer opens it by its reference number - answers, documents and process are on the case - assigns it to themself and takes it on.

Step 9. Decide: Review Application

Case Officer · Back office

At "Review Application" the Case Officer records the decision: approve, with a comment kept in the case history. Approving moves the case on; the last decision completes it and issues the document.

Step 10. Issue the document

Case Officer · Back office

The service's validity ("N/A") is not a fixed period, so completing the case does not issue the document by itself: the officer issues it from the completed case ("Issue / check permit"). It is generated from the service's output configuration and sealed.

Step 11. The document in My permits

Citizen · National e-Services portal

The issued document (MMMD-AR-2026-00001 in this run: "Authorized Registration") is listed in "My permits and licences" with its validity and a download of the sealed PDF.

Step 12. Verify the document

Anyone (public) · Public verification page

The QR code on the document opens the public verification page: genuine and current, to whom it was issued, and whether the electronic seal is valid. No sign-in is needed.

3. Payment

Item	In the test run
Fee (as published)	None

4. Output documents

Authorized Registration (sealed PDF)

Issued when the case was approved, from the service's output configuration (permitDocument/issued@1), filled from the application and the decision, sealed with the platform's electronic seal and stored as the issued version. The holder downloads it from My permits; the verification page checks it.

The issued PDF has 1 page; the image shows the first.

Fields

Field	Value in the test run
Document title	Authorized Registration
Permit / licence number	MMMD-AR-2026-00001
Holder	Chanda Mwila
Valid from	2026-10-21
Valid until
Status	active
Verification code (printed with a QR code)	BAWB-6PPL-74

Seal

Item	Detail
Seal status	sealed
Signature level	PAdES-B-T
Sealed by	the platform seal (development key in the test run)
Signed at	2026-10-21T08:30:25.002Z
Trusted time-stamp	2026-10-21T08:30:26.323Z (time-stamping authority)
Document fingerprint (SHA-256)	6b6d0c0002fdcd13...

Verification

Item	Detail
Where	The public verification page of the national portal, <portal>/verify/<verification code>, opened by scanning the QR code on the document.
What it shows	Whether the document is genuine and current, its holder and validity, and whether the electronic seal is valid and who sealed it.
Checking a copy	Anyone can upload a PDF they were given; the page says whether it is exactly the document that was issued. A changed copy is reported as not matching.

On screen: step 10 (Issue the document), step 11 (The document in My permits), step 12 (Verify the document) in section 2.

5. Notifications

When	Channel	To	Message	Delivery
Application received	in-app (portal bell)	the applicant	Application MMMD-AR/00001/10-21-26 received - Your application MMMD-AR/00001/10-21-26 for Authorized Registration has been received by Cadastre Department.	shown
Status changed	in-app (portal bell)	the applicant	Update on application MMMD-AR/00001/10-21-26 - MMMD-AR/00001/10-21-26 (Authorized Registration) is now: With the office - awaiting approval.	shown
Invitation to rate the service	in-app (portal bell)	the applicant	How was Authorized Registration? - How was Authorized Registration? Tell us in about a minute.	shown
Decision: approved	in-app (portal bell)	the applicant	Application MMMD-AR/00001/10-21-26 completed - MMMD-AR/00001/10-21-26 (Authorized Registration) is complete. Your documents are ready.	shown
Licence / permit issued	in-app (portal bell)	the applicant	Your Authorized Registration document has been issued - MMMD-AR-2026-00001 has been issued for Authorized Registration.	shown
Application received	email	e2e.c***@example.test	Application MMMD-AR/00001/10-21-26 received	skipped
Application received	sms	+260 97* *** 567	Application MMMD-AR/00001/10-21-26 for Authorized Registration has been received. Track it: <portal>/my-workplace	delivered
Status changed	sms	+260 97* *** 567		delivered
Invitation to rate the service	sms	+260 97* *** 567		skipped
Invitation to rate the service	email	e2e.c***@example.test	How was Authorized Registration?	skipped
Decision: approved	sms	+260 97* *** 567		delivered
Decision: approved	email	e2e.c***@example.test	Application MMMD-AR/00001/10-21-26 completed	skipped
Licence / permit issued	email	e2e.c***@example.test	Your Authorized Registration document has been issued	skipped
Licence / permit issued	sms	+260 97* *** 567		delivered

Delivery: shown = in the portal's notification bell; delivered = the SMS gateway (a test double in this run) reported the text delivered; skipped = not sent on that channel (e-mail is not configured on the test installation, and some notices go out on one channel only); sent by the national portal = a ministry node handed the notice to the national portal, which texts and e-mails the citizen under its own name and the citizen's preferences. Addresses written <portal>, <ZamPay> stand for the national portal and ZamPay.

6. Legacy mapping

Item	Detail
Replaces	Authorized Registration in the legacy ZIGS e-Services directory (ZIGS_Services)
Legacy service id	464
Legacy provider	Cadastre Department (MMMD) under Ministry of Mines and Minerals Development
Legacy process	not recorded
Fee in the legacy system	none
Fee taken before submission	yes (as in ZIGS)
Time to issue (legacy)	New: 5 working days
Legacy output templates	GS-1 Application for a Government Service: ZIGS_Forms_ZDA / GS1 GS-2 Notice of Government Action: ZIGS_Forms_Notices / GS-2.NoticeOfAction
Legacy address	https://mmmdui.gsb.gov.zm
How it was brought over	Imported by the platform's legacy catalogue importer (zcm-backend scripts/zigs/importLegacy.js) from the ZIGS snapshot: form, case types, fees, documents, process and output templates, then served by the new platform.

7. Version and date

Item	Detail
Document version	service v1, platform a0a302b8
Generated	2026-10-21T08:30:32Z (by the end-to-end run, not edited by hand)
Service version	not versioned (configured directly)
Platform snapshot	backend a0a302b8 portal 72805f0 back office 58e5946
Test suite	e2e 5999d9b; one installation (combined); seed profile mihud
Journeys	30-catalogue-service.spec.js: citizen finds the service, answers its form, uploads its documents and sends the application - passed 30-catalogue-service.spec.js: the case goes through every step of its process: payments by the citizen, each officer step by its role - passed 30-catalogue-service.spec.js: the grant document is issued, sealed, filled in and verifiable; the citizen has it in My permits - passed
Result	3 of 3 journey tests passed
Data	Synthetic test data on a local test installation; provider test doubles for ZamPass, ZamPay, SMS and signing.