Permission roles

Tutorials and guides for the features of Octaved Flow

Permission roles define the extent to which a user may view, edit and create projects, work packages, tasks or board posts.
The following permission roles can be set for a user:
Permission roles
  • Reader - Users with this permission role can see everything in the projects, but cannot edit anything.
  • Standard - Users with this permission role can do everything they need to do to complete work packages. This includes, for example, marking work packages as completed, creating and checking off tasks, writing board posts and tracking times in projects. The Standard permission role cannot be used to perform actions that are reserved for project managers and department heads. It is not possible to create and delete projects and work packages, view prices, edit commercial details such as maximum effort, assign responsible persons, plan work packages and change their planning.
  • Full - The Full permission role contains all permissions for projects, sub-projects and work packages. It is usually assigned to project managers, department heads and managing directors.
  • None - This permission role cancels out inherited permission roles. Users with this permission role have no access.

Application of permission roles

Permission roles can be defined for users and groups on project folders 1 and then apply to all projects in the respective project folder:
Projectfolder with permission roles
In addition, permission roles can also be assigned in connection with project roles in order to increase the permission level so that the user has the necessary permissions to be able to perform their role. 1
Project role with permission role
More about project roles in the Project roles tutorial.Open tutorial
dot background image