Roles control what a staff member can see and do within a municipality. Give people the access their work requires, and review access when their responsibilities change.
Understand default roles (link to section)
| Role | Typical responsibilities |
|---|---|
| Administrator | Manage the municipality’s configuration and access. |
| Supervisor | Oversee case work, assignments, payments, and operational jobs. |
| Processor | View and act on cases, and view services. |
| Service builder | Create and edit services and participate in review. |
| Publisher | Review and publish services. |
| Auditor | Read authorized records and export cases without changing them. |
An organization can use custom roles. Check the actual permissions assigned rather than relying only on a role’s name.
Separate building from publication (link to section)
The service builder role does not grant publication by itself. A publisher can release a reviewed service; an administrator has all permissions.
Use this separation when one person prepares a process and another is responsible for its release. See Review and publish.
Treat access management as full trust (link to section)
Someone who can manage roles can grant permissions, including powerful permissions. Treat this access as administrator-equivalent.
Civiture preserves at least one active administrator. The built-in Administrator role cannot lose its permissions, and system roles cannot be deleted or converted into other roles.
Check profile ownership (link to section)
Some identity fields are managed by a connected directory. Directory-managed values take precedence over administrator or personal changes.
An administrator can edit eligible profile details only for staff who belong to that municipality alone and whose fields are not directory-managed. Ask the identity administrator to correct a managed field at its source.
Review recorded changes (link to section)
Role changes, access status changes, membership changes, and role configuration changes are recorded in the audit log with the actor.
Review access when staff join, move departments, or leave. Use individual accounts so the record identifies the person who acted.