Version Review Queue

The Admin → Versions page gives administrators a queue of all GIS versions that have been submitted for review by non-admin users. Admins approve or reject each version before it becomes visible to the rest of the team.

Why a Review Queue?

Field workers and GIS editors can create and edit map features offline, but their changes need to be checked before becoming part of the shared dataset. The review queue provides that checkpoint:

• Quality control — verify geometry is correct before it goes live
• Compliance — ensure changes follow organisational standards
• Safety — prevent accidental overwrites of shared infrastructure data

Admins bypass this queue — their own submissions commit directly without review.

Version States

A version has no single stored status field. Its state is derived from a few fields:

There is no persisted "draft" state. A version in progress locally simply has not been submitted (submittedForReview is not set) and has no committedAt.

Reviewing a Version

Finding Pending Versions

1. Navigate to Admin → Versions
2. The default view shows versions pending review (submitted but not yet committed)

Each row shows:

• Version name (or auto-generated ID)
• Owner (the first of the version's owners)
• Date and time
• Whether it is committed

A version carries an owners list, not a single submitter — one or more users who own the version.

Inspecting a Version

Click a version row to open the detail view:

• Feature diff — what was added, changed, or deleted
• Map preview — the affected features highlighted on the map
• File attachments — photos or documents attached to the version

Approving (Committing)

1. Review the diff and map preview
2. If satisfied, click Commit
3. The version's committedAt is set
4. All features in the version become immediately visible to all users
5. The owner receives a notification (if push notifications are enabled)

Deleting

1. Click Delete Version
2. Confirm the deletion (a plain confirmation — there is no rejection note)
3. The version's stamp.deletedAt is set
4. The owner's local draft is not automatically discarded — they can revise and resubmit

Version History

The Versions page also shows the complete history of all committed versions, not just pending ones. This serves as an audit trail:

• Who submitted what, and when
• Which admin committed or deleted it
• All features affected by each version

This history is permanent — committed versions are retained as the audit record.

Notifications

Admins receive notifications when new versions enter the queue (requires push notification subscription). Owners receive notifications when their version is committed or deleted.

See Notifications for how to subscribe to push notifications.

Scheduled Import Versions

Background import jobs (from GIS file uploads) also create versions automatically when they complete. These appear in the Versions page and follow the same review process.

Permissions

The Versions page itself is gated on the adminRightsModify admin right. Committing a version additionally requires either allowCommits or adminRightsModify — the Commit button only appears when the user holds one of those.