Plans and pricing

Roles and permissions

Understand how your user role affects project, data and administration actions.

Last updated:

On this pageFind your roleSettings requiring administration permissionModule visibilityIf an action is unavailable

Find your role

The user menu at the top right shows your role and organisation. The read-only role is labelled Viewer.

Action Super administrator Organisation administrator Editor Viewer
Access scope Across organisations Own organisation Own organisation Own organisation
View projects and data Yes Yes Yes Yes
Obtain reports/outputs and export Yes Yes Yes Yes
Create projects Yes Yes Yes No
Draw, edit and import Yes Yes Yes No
Undo data operations from history Yes Yes Yes No
Archive and permanently delete projects Yes Yes No No
Manage organisation users Yes Own organisation No No
Manage organisation basemaps Yes Own organisation No No
Read data in disabled modules Yes Own organisation No No

This table shows the general scope of organisation roles. Project access also depends on project membership; writing depends on the project role and selected module/area scope. Write permissions apply only if the relevant module is enabled and the licence allows the action. Organisation allowances may also restrict adding projects, users or data. A full package of a project containing disabled-module data can only be downloaded by an administrator authorised to read that data.

Organisation administration shows the permission context; project membership is assessed separately.

Settings requiring administration permission

An organisation administrator manages user roles and active status within their organisation. A super administrator can access other organisations' administration. The screens available for organisation creation, allowance and module management depend on the deployment type.

Project settings do not all require the same permission. The effective project role is determined by considering the organisation role and project membership together. Project manager permission does not grant authority to manage organisation users; module, policy, approval and publication actions follow their respective screens' administration requirements. Use the actions offered by the relevant screen as your guide.

Module visibility

Disabling a module does not delete its data. Authorised administrators can inspect these records with Show data from disabled modules (read-only) in Layers. This does not grant editing permission; undo operations affecting disabled-module records are unavailable too.

If an action is unavailable

  1. Check your role in the user menu.
  2. Confirm that you are in the correct organisation and project.
  3. Check project membership and writable module/area scope, and confirm that the relevant module is enabled.
  4. Read the displayed licence or allowance explanation.
  5. If permissions have changed, follow the open form's warning and reopen the project to check available actions.

See Organisation administration, Project settings and Licence states for more information.