Publication makes a reviewed service configuration available for new requests. Treat it as the point where your municipality confirms the form, route, assignments, and applicant information are ready.

Check your permissions (link to section)

Service editing, review, and publication are separate permissions. A service builder can prepare a draft while a publisher handles publication.

If you cannot perform a required action, ask an administrator to check your role. Read Staff and roles for the default access model.

Preview the draft (link to section)

Work through the service using fictional applicant details. Preview is for checking the draft; saving the draft alone does not change what residents see.

Check:

  • The service name, eligibility, requirements, and contact information.
  • Question labels, help text, required answers, and conditional paths.
  • Staff assignments and each possible decision outcome.
  • Notification recipients, subjects, and messages.
  • Document mappings and sample output, if the service generates documents.
  • Booking rules, available spaces, approval steps, and payment order, if applicable.

Resolve review issues (link to section)

Open the service’s review stage and address the reported configuration problems. A route must be connected and able to reach an end. Referenced answers and templates must be available in the configuration being published.

If you edit after review, check the resulting draft again. The configuration you publish should be the one you reviewed.

Review automated checks and the applicant experience together. A valid route still needs instructions, assignments, and wording that make sense to the people using it.

Publish a version (link to section)

Have an authorized publisher publish the reviewed service. Publication creates an immutable version of its configuration.

New requests use the active published version. Existing cases retain the service version they started with, including its route and document template configuration.

Make a later change (link to section)

Edit the draft, preview the change, and repeat review and publication. Check the version history when you need to understand which configuration a service used.

Changing a shared template does not silently replace a template already copied into a service. See Documents and emails before updating reusable content.