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:
| Permission | Allows | Default roles |
|---|---|---|
dictionaries.manage | Administration › Dictionaries: edit choice lists, priced items and rates, and export or import them | Administrator |
jobs.manage | Administration › Background jobs: see map scans and spatial checks, and retry failed ones | Administrator |
conflicts.resolve | Decide conflicts on Records › Conflicts: merge, keep existing, accept the new information, not a conflict | Administrator, Compensation Officer |
spatial.resolve | Accept or reopen spatial flags on Records › Spatial flags, and run the spatial checks again | Administrator, Compensation Officer |
| Page | Who 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 gaps | properties.manage or claimants.manage |
| Records › Conflicts | Read: claimants.view. Decide: conflicts.resolve |
| Records › Spatial flags | Read: properties.view. Accept or reopen: spatial.resolve |
| Administration › Dictionaries | dictionaries.manage |
| Administration › Background jobs | jobs.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 outlines | subboundaries.manage (import also needs data.import); projects.view to see |
| Field teams: assign agents to areas, change the lead, end an assignment | surveys.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 activity | surveys.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 note | claimants.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 batches | settings.manage |
| Saved views: save a register’s filters; share them | Anyone, 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 reports | reports.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 log | ai.manage |
| A property’s boundary and items | properties.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 downloads | data.export |
Rules that apply to everyone
- Administrator is a locked system role: it always has every permission, including ones added in future versions.
- No-one can grant more access than they have. Only an Administrator can assign the Administrator role or change an administrator’s account; other staff managers can only assign roles whose permissions they hold themselves.
- You cannot change your own role, disable yourself, or remove
roles.managefrom your own role. - Field roles: a role whose only permission is
survey.fieldcan use the field app only, and its sessions last 30 days so the app keeps working offline. Office roles’ sessions last 12 hours. - Each compensation step has its own permission, so for example a Valuer cannot approve and Finance cannot value.
- Sensitive numbers (account number, BVN, NIN, ID number) are masked for everyone.
claimants.revealadds a Reveal button and the option to export full numbers (including in the payment schedule); all are minuted. - Field roles capture properties and claimants under Field capture with
survey.fieldalone; no office permission is needed. They work in the areas assigned to them (plus 200 m);field.all_projectslifts that. - Export and import also need the view or manage permission of the register concerned.
- Changes to a role apply at each holder’s next request.