Roles and permissions

A role is a named set of permissions. Every action the server performs checks one, and the office app hides what your role cannot use. Administrators edit roles on the Roles page; the defaults below are what a new installation starts with.

Default roles

Your organisation may have changed these or added others. To see your own: My account › Your access. To see anyone’s: Staff › open the person › What this role can do.

Who can do what

✓ = the default role has the permission. Hover a column heading for the full role name.

Pages and the permissions they need

The permissions added with field capture, boundaries and the new compensation module:

PermissionAllowsDefault roles
dictionaries.manageAdministration › Dictionaries: edit choice lists, priced items and rates, and export or import themAdministrator
jobs.manageAdministration › Background jobs: see map scans and spatial checks, and retry failed onesAdministrator
conflicts.resolveDecide conflicts on Records › Conflicts: merge, keep existing, accept the new information, not a conflictAdministrator, Compensation Officer
spatial.resolveAccept or reopen spatial flags on Records › Spatial flags, and run the spatial checks againAdministrator, Compensation Officer
PageWho sees it
Map (system map of every project boundary, coloured by status; zoom in to see properties)projects.view — every office role
Records › Fill the gapsproperties.manage or claimants.manage
Records › ConflictsRead: claimants.view. Decide: conflicts.resolve
Records › Spatial flagsRead: properties.view. Accept or reopen: spatial.resolve
Administration › Dictionariesdictionaries.manage
Administration › Background jobsjobs.manage
A project’s boundary and map scan (analytics only)projects.manage to change; projects.view to see
Sub-boundaries: draw, edit details and outline, archive, colour, import outlinessubboundaries.manage (import also needs data.import); projects.view to see
Field teams: assign agents to areas, change the lead, end an assignmentsurveys.assign; surveys.view to see the teams and workload. Only staff whose role has survey.field can be assigned
Work queues › Field work: each field officer’s areas, captures, surveys and activitysurveys.assign or surveys.review for every officer; the lead of an area sees the people of the areas they lead, without either permission
The field app on every active project (not only the areas assigned)field.all_projects — given to roles that assign surveys (supervisors)
Work queues › Integrity: see the hints; set one aside with a noteclaimants.view (or conflicts.resolve) to see; conflicts.resolve to set aside
Registers › Payment batches: prepare and check a batch; approve it (not one you prepared)payments.batch (Finance, Compensation Officer); payments.approve (Finance)
Administration › Rules: four-eyes, second approval, collection code, cheques from batchessettings.manage
Saved views: save a register’s filters; share themAnyone, for the registers they can open; a shared view is offered only to those who can open its register
Outreach › Reports: write, check, print and email reportsreports.view — Compensation Officer, Finance and Viewer / Auditor by default. Scheduling overnight reports: reports.manage
AI suggestions: ask for one (a person always decides)ai.use — Compensation Officer, Valuer and Finance by default
AI: read ID cards and land documents (when switched on)ai.documents
Administration › AI: switches, models, budgets, test calls, the logai.manage
A property’s boundary and itemsproperties.manage to change; properties.view to see
Value a case on its worksheet (each save is a version)comp.valuate, before approval; after approval also comp.correct (the case goes back to Valuated)
Payment schedule and map data downloadsdata.export

Rules that apply to everyone