Service Configuration

The Citizen Service Portal Administrator maintains the services that an organization offers. Each definition has a name and code, an owning organization, effective dates and a policy reference. Operators use that definition when registering a beneficiary application. Clear service names help staff select the right route before they collect requirements or ask for review.

Organization and staff records supply the responsible agency and people behind the case. Their active state helps the setup team review which entries are intended for current use. Keep those records aligned with actual staffing and service ownership. A service definition should give the next operator enough context to understand which organization’s policy applies.

• Service policy. Maintain the service code, effective period and policy reference with the definition. Review these details before using a service for the pilot so staff recognize the correct program.
• People and organizations. Keep staff codes, contact details and organization references understandable. Confirm account access and assigned responsibilities before expecting an operator to work from their personal queue.
• Source mapping. Document source and target fields, their types and transformation rule when setting up a data connection. Keep the mapping version and effective date with the related service definition.

Agree who owns changes to service definitions and who maintains staff and organization records. The Citizen Service Portal Administrator manages service definitions within their permissions. Admin handles the agreed setup configuration. Neither responsibility substitutes for the Citizen Service Portal Reviewer’s independent decision on an application.

If requests will arrive from another system, choose a source identifier and map the payload into the application and requirement fields. Review how the citizen reference and service code are represented before importing real cases. A reviewed mapping describes the intended transfer; the actual connection still needs its own implementation and rehearsal. Keep provider credentials outside case records and limit the data transferred to the agreed purpose.

Use an illustrative community support service with an effective date and policy reference. The administrator creates the service definition under the intended organization. The setup team confirms the operator and reviewer belong to the right operating context. The operator then registers an application and explains why that definition is the appropriate choice.

For an imported request, take a representative source payload and compare the mapped citizen reference, service code and requirement source identifier with the resulting case. Include a source value that needs transformation, then inspect the result with the responsible administrator. If the mapping changes, retain its version and effective date so later staff can explain which instructions were used. Complete this rehearsal before expanding the connection to a wider intake.

• Active Public Services — Review service definitions, their effective periods and policy references.
• Source Mapping Register — Inspect dated mapping instructions and the service definition they support.

Begin with application intake. Agree connection responsibilities in implementation before importing requests.