Getting Started: User Permissions in Mastt
Simple guide to who can access what in your construction projects
Mastt's permission system controls who can see and edit your construction projects. Understanding how it works helps you give the right people the right access without creating security issues or confusion.
How permissions work
Think of permissions like building access - some people have keys to the whole building (workspace), some have access to specific floors (programs), and others only have keys to individual offices (projects).
The three main areas
Workspaces are like your company divisions or office locations. Examples: "Admin Workspace" or "Engineering Workspace"
Programs are collections of related projects. Examples: "Program A" or "Infrastructure Program"
Projects are individual construction jobs. Examples: "Project A" or "Project B"
Permission levels explained
Read permission - You can view information but can't change anything. Like having a visitor pass.
Write permission - You can view and edit project information like costs, risks, and schedules. Like having an employee access card.
Admin permission - You can do everything including managing users and settings. Like having a master key.
How access is inherited
Workspace access flows down
If you're an admin of "Admin Workspace" workspace, you automatically get admin access to all projects and programs in that workspace. You don't need separate permissions for each project.
Example: Sarah is admin of "Admin Workspace". She automatically has admin access to "Program A" and "Project A" within that workspace.
Program access has special rules
If you're admin of a program, you get different access depending on where projects are located:
- Admin access to projects in the same workspace as your program
- Read access to projects from other workspaces that are part of your program
Example: Tom is admin of "Program A" in Admin Workspace. The program includes:
- "Project A" (also in Admin Workspace) - Tom gets admin access
- "Project B" (in Engineering Workspace) - Tom gets read access
Why Some Projects Show on Your Home Page (and Others Don’t)
Assigned Projects - These are projects you’ve been specifically added to. They’ll appear on your home page and project lists because you’re expected to actively work on them.
Permission-Based Projects - These are projects you can open and view because you have access through a workspace or program — but you’re not directly assigned. They won’t show up on your home page unless you're added to them.
Example: Lisa is an admin in the "Engineering Workspace," so she can open any engineering project. But only the projects she’s been assigned to will appear on her home page for quick access.
Common permission setups
Project Manager
- Direct admin access on their specific projects
- Read access to related programs for context
Program Director
- Admin access on their program
- Direct access to key projects they're actively involved in
Team Member
- Write access on projects they contribute to
- Read access to programs for reporting and context
Client or Stakeholder
- Read access on specific projects or programs they need to monitor
Setting up access the right way
Create projects
Create projects for your construction work and assign them to the appropriate workspace. Each project should belong to one workspace that matches your organisational structure.
Invite users
Add team members to the appropriate workspaces, programs, or projects based on their role and responsibilities.
Use programs for oversight
Set up programs for people who need to see across multiple related projects but don't need full workspace access.
Troubleshooting and FAQ
Q: Someone needs access to a project from another workspace, how do I do this?
Add them directly to that specific project from the project settings view.
Q: What's the difference between being able to access something and being assigned to it?
Assignment means that someone has explicitly added you to a project, you will then see that project in your home page or my project page.
Workspace Admin users can access projects that they aren't assigned to from the admin module.
Users who are not Workspace Admins cannot access a project unless explicitly assigned to it.
Q: How do I give someone oversight of everything without cluttering their home page?
Make them a workspace admin. They'll have access to everything in that workspace from the admin module but only directly assigned projects will appear on their home page.
Getting help
If you're unsure about someone's access level or need to change permissions, contact your workspace admin or Mastt support. They can review the setup and make sure everyone has the right access for their role.