Understanding Permissions in Mastt
Complete guide to permission levels and access control for construction project managers
Mastt's permission system controls what users can see and do across your workspaces, programs, and projects. Understanding these permission levels helps you manage team access effectively while maintaining project security.
Permission levels explained
Viewer - Read-Only Users can view information but cannot make changes. Best for stakeholders who need visibility without editing rights.
Standard - Read and Write Users can view and edit content within their assigned areas. Ideal for team members actively working on projects.
Administrator Users have full control including user management and settings. Reserve for project leaders and senior management.
How permissions are assigned
Direct assignment Users are explicitly given permissions on specific workspaces, programs, or projects. These permissions show up as records in your user profile.
Inherited permissions Users automatically receive permissions on lower-level resources when they have permissions on higher-level ones. For example, being a Workspace Admin automatically gives you admin rights to all programs and projects in that workspace.
Project visibility Projects only appear on your dashboard when you're directly assigned to them. You might have access to other projects through your workspace or program permissions, but they won't show up unless you're specifically assigned.
Workspace ownership matters Every project and program belongs to exactly one workspace. The workspace that owns a resource determines how permissions cascade down.
Workspace permissions
- Admin: Full control over the workspace, all programs, and projects
- Member: Basic access to assigned projects and programs only
Program permissions
- Admin: Manage the program and all projects within it, and reopening cash flow months
- Write: Edit program content and assigned projects
- Read: View program information only
Project permissions
- Admin: Full project control including user management, and reopening cash flow months
- Write: Edit project content and data
- Read: View project information only
Permission inheritance
Higher-level permissions automatically include lower-level access:
- Workspace Admins have admin access to all programs and projects in that workspace
- Program Admins have admin access to all projects within that program in the same workspace
- Project assignments only affect that specific project
Cross-workspace scenarios
When projects span multiple workspaces, inheritance works differently:
- Workspace Admins only get read access to projects owned by other workspaces if their workspace has been invited to a project.
- Program Admins only get read access to projects that belong to other workspaces if that project is part of their program.
- Direct assignment is required for full access to projects owned by other workspaces
Important considerations
Workspace Admin is powerful Workspace Admins can access and modify everything in the workspace. Only assign this role to trusted senior team members.
Cross-workspace projects When projects span multiple workspaces, users only get read access to projects owned by other workspaces, even if they're program admins.
Assignment vs access Being assigned to a project makes it appear on your dashboard. However, you might have access to other projects through your workspace or program permissions.
Best practices
Start with minimal access Give users the minimum permissions needed for their role. You can always increase access later.
Review regularly Audit user permissions monthly, especially after team changes or project completions.
Use workspace structure wisely Organize workspaces by department or project type to simplify permission management.
Document your approach Keep a record of who has admin access and why, particularly for compliance requirements.
Common scenarios
New team member Start with Read access to relevant projects, then increase to Write as they become more involved.
External consultant Assign project-specific permissions rather than workspace-level access to maintain security.
Project handover Transfer admin permissions to the new project manager and remove admin access from the departing manager. Review and adjust other team members' access levels based on their continued involvement. If the project moves to a different workspace, you'll need to reassign users as the inheritance structure changes.
Getting help
Contact your workspace administrator if you need access to projects or programs. For permission-related issues, provide your current role and what you're trying to access.