Civiture brings a municipality’s service forms and the work behind them into one workspace. A resident submits a request through a published service. Staff then process the resulting case using the route that service defines.

This documentation is for municipal staff, service builders, and administrators. The examples use fictional places, including Lakeview.

How the pieces fit together (link to section)

TermWhat it means
ServiceA complete process, such as renting a hall or applying for a permit.
FormThe questions a person answers when requesting a service.
RouteThe connected steps that move a request toward an outcome.
CaseOne submitted request and the work, files, and decisions attached to it.
Published versionThe reviewed configuration used for new requests.

A service can collect a form, assign a task, ask for a decision, send a notification, and finish with an outcome. The exact sequence depends on the service.

Choose where to start (link to section)

Work within your role (link to section)

The pages and actions available to you depend on your municipality’s roles and permissions. Someone who processes cases may not be able to edit services. Someone who builds a draft may need a publisher to release it.

If an action is unavailable, ask your municipality’s administrator to check your access. Do not share accounts to work around a missing permission.

Understand drafts and live services (link to section)

Changes in the builder belong to a draft. Saving a draft does not change the published service residents use.

Publication creates a version for new requests. Existing cases continue to use the version they started with, so an edit does not unexpectedly change work already underway.

Before publishing, preview the form and follow the route through every possible outcome. See Review and publish for a practical checklist.