Understanding Access Levels in CxPlanner
To ensure your team has the right access to tools and information, CxPlanner uses a three-level access structure. This guide will help you understand how roles and permissions are organized across the Platform, Projects, and User-groups.
This level controls access across the entire CxPlanner platform. It is not tied to specific projects.
Administrator
Can grant platform access
Manage users
Modify company settings
Moderator
Can create new projects
User
Can be added to projects but has no platform-level permissions
π Note: The company role affects your license access only and can generally be ignored unless assigning internal PMs as Moderators.
These roles are project-specific and operate independently from company-level roles. You can be a regular user at the company level and still be a Project Administrator.
Internal Project Roles:
Administrator
Manager
External Project Roles:
Consultant
Designer
Contractor
Viewer
π Tip: A userβs company role does not impact their ability to manage or participate in projects.
User-groups allow you to fine-tune what users can see and access within a project.
Use Cases:
Limit the view
Restrict visibility to only assigned tasks
Ideal for subcontractors or vendors
Access to files
Provide group access to specific folders in the file module
π Best Practice: Use User-groups to control information flow and enhance collaboration efficiency.
1. Platform/License Level β Company Role
This level controls access across the entire CxPlanner platform. It is not tied to specific projects.
Roles:
Administrator
Can grant platform access
Manage users
Modify company settings
Moderator
Can create new projects
User
Can be added to projects but has no platform-level permissions
π Note: The company role affects your license access only and can generally be ignored unless assigning internal PMs as Moderators.
2. Project Level β Project Role
These roles are project-specific and operate independently from company-level roles. You can be a regular user at the company level and still be a Project Administrator.
Internal Project Roles:
Administrator
Manager
External Project Roles:
Consultant
Designer
Contractor
Viewer
π Tip: A userβs company role does not impact their ability to manage or participate in projects.
3. User-Groups β Segmenting Project Roles
User-groups allow you to fine-tune what users can see and access within a project.
Use Cases:
Limit the view
Restrict visibility to only assigned tasks
Ideal for subcontractors or vendors
Access to files
Provide group access to specific folders in the file module
π Best Practice: Use User-groups to control information flow and enhance collaboration efficiency.
Summary
Level | Purpose | Examples |
---|---|---|
Company Role | Platform/license access | Admin, Moderator, User |
Project Role | Per-project access and permissions | Project Admin, Contractor, Viewer |
User-Groups | Segment visibility and file access in projects | Subcontractor file access |
Updated on: 04/02/2025
Thank you!