Admin & Setup
Security roles control what each user can see and do in ProjectSight. Configuring roles is a required step during implementation and ensures your team has the right level of access.
|
Review out-of-box roles ProjectSight comes with pre-defined roles. Download the Security Roles template to see what's available and use it as your starting point. |
|
|
Define your roles Think about the roles your organization needs. Common examples: Portfolio Admin (highest level), Project Manager, Team Member, Viewer. Portfolio Admin must always be your highest access level. |
|
|
Assign module access For each role, decide what they can access: Portfolio settings, Project settings, record features, and Reports. You can mark access as Yes or No for now—we'll refine the details together. |
|
|
Set record permissions For each record type, mark what users can do: V (View), C (Create), M (Modify), R (Remove). This controls their ability to interact with specific data. |
|
|
Share with your TAM Once you've completed the template, share it with your Technical Account Manager. They'll review it with you and configure the roles in ProjectSight. |
| ⚠️ Important: Security roles must be configured before your team can start using ProjectSight. This is a required implementation step. Your TAM will guide you through this process. |
| What to prepare: • Security Roles template (download below) • List of team members and their roles • Clarity on what each role needs to access • 30–60 minutes to complete the template |
Comments
Article is closed for comments.