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

Reviewing a Version

Finding Pending Versions

1. Navigate to Admin → Versions
2. The default view shows only submittedForReview versions
3. Use the status filter to see committed or deleted versions as well

Each row shows:

• Version name (or auto-generated ID)
• Submitter (user who created it)
• Submission date and time
• Number of features affected
• Geometry types (points / lines / polygons)

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
• Conflict indicator — if another version overlaps the same features
• 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 state changes to committed
4. All features in the version become immediately visible to all users
5. The submitter receives a notification (if push notifications are enabled)

Rejecting (Deleting)

1. Click Delete Version
2. Optionally add a rejection note (visible to the submitter)
3. The version state changes to deleted
4. The submitter'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 — versions are never fully erased, only compressed.

Conflict Detection

When two users submit versions that affect the same features or overlapping geography, a conflict is flagged:

• The second version to arrive is marked as conflicting
• Both versions remain in the queue
• Admin can view both diffs side-by-side
• Admin chooses which to commit first (or requests the submitters coordinate)

Notifications

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

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 with the submitter shown as system. They follow the same review process unless auto-commit is enabled for imports in Admin → Settings.

Permissions