Skip to main content
Categories
Table of Contents
< All Topics
Print

ConstructMind uses a two-tier role model: organisation-level roles control what a user can do across the platform, and project-level roles control what they can do within a specific project.

Organisation-Level Roles

Every user belongs to an organisation and is assigned one of the following three roles:

Org Roles & Permissions
Role Best For Key Permissions
Org Admin System administrator or IT owner Create and archive projects, manage all users, configure organisation settings, view all projects in the organisation.
Org Manager Senior PMs overseeing multiple projects Create projects (auto-assigned as Project Owner), invite and manage org users, view all projects.
Org Member Planners, engineers, contributors Work within projects they are assigned to. Cannot create projects. Access limited to their assigned projects only.
Org Admin System administrator or IT owner
Key Permissions
Create and archive projects, manage all users, configure organisation settings, view all projects in the organisation.
Org Manager Senior PMs overseeing multiple projects
Key Permissions
Create projects (auto-assigned as Project Owner), invite and manage org users, view all projects.
Org Member Planners, engineers, contributors
Key Permissions
Work within projects they are assigned to. Cannot create projects. Access limited to their assigned projects only.


IMPORTANT
Org Members cannot create projects, nor can they request project creation. Only Org Admins and Org Managers have project creation rights.


Project-Level Roles

Within each project, users hold a project-level role that may differ across projects. A user might be a Lead Planner on one project and a Contributor on another.

Role Best For Key Permissions
Project Owner Accountable schedule owner Full workflow access (Generate, Review, Assess), approves assumptions, commits the schedule, unlocks and downloads XER export, manages project team.
Lead Planner Primary scheduler Full workflow access, can approve assumptions. Cannot commit the schedule for final export.
Contributor Document controllers, engineers Upload project documents. Read-only access to schedule outputs and Basis of Schedule. Cannot run or modify workflows.
Read Only Clients, stakeholders View project documents, schedule outputs, and Basis of Schedule. No upload, edit, or workflow access.

Project Owner Accountable schedule owner
Key Permissions
Full workflow access (Generate, Review, Assess), approves assumptions, commits the schedule, unlocks and downloads XER export, manages project team.
Lead Planner Primary scheduler
Key Permissions
Full workflow access, can approve assumptions. Cannot commit the schedule for final export.
Contributor Document controllers, engineers
Key Permissions
Upload project documents. Read-only access to schedule outputs and Basis of Schedule. Cannot run or modify workflows.
Read Only Clients, stakeholders
Key Permissions
View project documents, schedule outputs, and Basis of Schedule. No upload, edit, or workflow access.


Permissions at a Glance

Permissions Matrix
Action Project Owner Lead Planner Contributor Read Only
Run Generate workflow
Run Review workflow
Run Assess workflow
Approve assumptions
View schedule & Basis of Schedule
Commit schedule
Export XER to Primavera P6
Manage project team
Invite external users


External Users

External users are invited directly to a project by the Project Owner. They do not hold an organisation account and cannot see any other projects or organisation settings. External users are automatically assigned the Read Only role and cannot be elevated to any other project role.