Permissions in the Application
Permissions within the application are designed to facilitate a secure and efficient workflow by assigning specific capabilities to users based on their roles. Understanding these permissions is crucial as they define what actions each user can perform, from creating and managing project content to merely viewing project progress. This section provides a detailed explanation of the different account types and roles, delineating the specific access each one has within the platform. By comprehending the permission structure, users can collaborate effectively while maintaining the integrity and confidentiality of the project information.
Account Role Definitions
TPM (Technical Project Manager):
A TPM is responsible for the technical aspects of project management. They have comprehensive permissions at the project level, which include updating project details, managing team members, and overseeing tasks and timelines. They can also create and manage prompts, meetings, and execution timelines.
PM / PM Manager (Project Manager / Project Management Manager):
PMs and PM Managers have a similar level of access to TPMs but with a focus on the overall project management process. They ensure that project goals are met by managing tasks, team members, and schedules. They have the authority to update project information and are involved in the creation of tasks, prompts, and meetings.
Others (FCA, Owner's Rep, etc.):
Other roles such as Financial Control Analyist (FCA) or Owner's Representatives have limited permissions focused on specific aspects of a project to which they are related. They may have the ability to contribute to tasks they are assigned but do not have the broad permissions to alter project details or manage other users.
Watcher:
Watchers have the most limited permissions, primarily with read-only access. They can observe project progress and leave comments on tasks, but they cannot modify project details or manage tasks and timelines. Their role is to stay informed about the project's development without actively contributing to management or administration tasks.
Project Level Permissions
| Action | TPM | PM / PM Manager | Others (FCA, Owner's rep) | Watcher |
|---|---|---|---|---|
| Update name | YES | YES | NO | NO |
| Update status | YES | YES | NO | NO |
| Update execution date | YES | YES | NO | NO |
| Add member | YES | YES | NO | NO |
| Replace member | YES | YES | NO | NO |
| Remove member | YES | YES | NO | NO |
| Create new task | YES | YES | if assigned to the task | NO |
| Update task status | YES | YES | NO | NO |
| Assign a member to a task | YES | YES | NO | NO |
| Update task actions | YES | YES | if assigned to the task | NO |
| Leave a comment on a task | YES | YES | YES | YES |
| Create prompt | YES | YES | NO | NO |
| Add notes to prompt | YES | YES | NO | NO |
| Add questions to prompt | YES | YES | NO | NO |
| Check off prompt question | YES | YES | NO | NO |
| Mark prompt as completed | YES | YES | NO | NO |
| Create meeting | YES | YES | NO | NO |
| Update meeting's info | YES | YES | NO | NO |
| Delete a meeting | YES | YES | NO | NO |
| Create execution timeline | YES | YES | NO | NO |
| Update execution timeline's info | YES | YES | NO | NO |
| Delete execution timeline | YES | YES | NO | NO |
| Create contact | YES | YES | NO | NO |
| Update contact's info | YES | YES | NO | NO |
| Delete contact | YES | YES | NO | NO |
Account Type Definitions:
Admin:
An Admin is the highest-level user within the application. Admins have full control over the platform, including the ability to create, update, and delete templates, invite and disable users, and create projects. They maintain the integrity of the system and are responsible for managing user access and permissions.
Super User:
Super Users have elevated privileges that include most of the capabilities of an Admin except for certain administrative controls. They can create and modify templates and have the authority to invite new users and disable existing ones. Their role is typically to support Admins in managing the platform and ensuring smooth operations within their scope.
User:
Users are standard-level accounts with permissions tailored to specific project files. They can create projects but cannot manage templates or user accounts. Their permissions are generally non-elevated, focusing on project-level activities and tasks they are assigned to.
Application Level Permissions
| Action | Admin | Super User | User |
|---|---|---|---|
| Templates (create/update/delete) | YES | YES | NO |
| Invite User | YES | YES | NO |
| Disable User | YES | YES | NO |
| Create Project | YES | YES | YES |