Organisation and user administration

Track organisation users, roles and usage allowances in the administration screens.

Last updated: 10 November 2026

Organisation scope

An organisation is the administrative workspace to which users and projects belong. Its administrator manages its users, projects and basemap settings. A super administrator can work across organisations. See Roles and permissions for details.

The organisation screen contains Users and Basemaps tabs. Defined allowances appear alongside user, project and storage usage.

Create a user

1. Open Users in the organisation administration screen.
2. Select New user.
3. Complete Full name and Username; add Email if needed.
4. Choose a Role appropriate to the person's work.
5. Set Password or select Generate.
6. Select Create user.
7. Send the resulting details to that user through a secure channel. The password is not shown again after the result window closes.

Passwords must contain at least 8 characters. A username or email already registered to another account is rejected. This screen cannot assign the super administrator role.

Edit an account

Search users filters by name, username or email. Select Edit on the relevant row.

• Leaving New password blank retains the current password.
• Clearing Calculation enabled deactivates the account and closes its sessions.
• A password change also closes existing sessions.
• Sign out all sessions closes active sessions without deleting the account.

An administrator cannot deactivate their own account or remove their own administrator role.

Organisation settings and deployment differences

In an on-premises deployment, a super administrator can select New organisation under Organisations. Set Organisation name, Short name and allowances, then select Create organisation. An existing organisation's Settings or Organisation settings screen manages its status, allowances and available modules.

In a centrally hosted deployment, organisation creation, allowances, modules and licence status are managed through the Control Centre. The corresponding application fields are therefore disabled. Organisation administrators continue managing users within the permitted scope. Users of a suspended organisation cannot sign in.

Interpret allowances

Change history is excluded from storage accounting. Archiving reduces the active project count; it does not delete project data or automatically release storage. Unarchiving and reactivating users are subject to allowance checks.

An organisation-level allowance does not override the overall installation licence allowance. When an allowance is reached, check the resource identified in the warning and contact the authorised administrator.

Layers and basemaps explains organisation basemaps; Licence states covers expiry and access warnings.