Project membership and area permissions

Determine who can access a project and which modules or areas they can edit.

Last updated: 10 November 2026

Organisation and project roles

Project membership adds project-specific access and work scope alongside the organisation role. Project roles are Project manager, Editor and Viewer. A user who is a viewer in the organisation cannot gain editing permission through project membership.

Module and area selections restrict writing only; they do not narrow readable data. An area permission is not a sharing setting that hides records outside the area.

Choose project access

1. Open Members in Project. The window is titled Project members.
2. As an authorised organisation administrator, choose Organisation users or Project members only under Project access.
3. Select Save access.

Organisation administrators can access all projects in their organisation. Save the access selection before editing members.

Add a member and define write scope

1. Select Add member.
2. Choose User and Project role.
3. For Writable modules, use the whole scope or choose Selected items only and select modules.
4. For Writable areas, choose Selected items only and select the relevant areas. The area features must already exist on the map to appear in this list.
5. Select Save and check Write scope in the member list.

Area and module selections do not expand the chosen project role's permissions. Actions affecting the whole project, such as creating a design or opening an as-built workspace, may require project-wide write permission.

Change membership

Use Edit on a member row to update the role or scope. Remove removes project membership. The user's organisation access is also assessed according to Project access.

If a form closes or displays a scope warning during a permission change, reopen the project and check current permissions. See Roles and permissions for organisation-level actions.