Permission Roles
Permission roles determine which permissions users or groups have, from read-only access to full editing rights. They apply to the current element and are inherited by the elements below it.
Permission roles determine which permissions users or groups have. The permission roles apply here and are inherited by the elements below them.
The permission roles have the following meaning:
- Reader - See everything except prices, no editing. If this permission role is set for a project folder, users can only view the projects but not edit them. If required, editing rights can then be assigned to users for individual projects.
- Reader (full) - See everything including prices, but not edit. Suitable, for example, for the management who also want to see the prices but want to restrict themselves to reading only.
- Standard - Everything you need to complete work packages. Among other things, check off work packages as done, work with tasks in the work package, create and edit posts on the board, track time for the work package. It is not possible to change the planning, assign responsibilities, edit the target effort and read and edit prices. The Standard permission is granted to users who work in the project and execute work packages.
- Full - All permissions for projects, sub projects and work packages, including changing the planning, assigning responsibilities, editing the target effort and reading and editing prices. For project managers (and department heads or managing directors).
- None - No access. Revokes inherited permissions. Used, for example, if the user is allowed to read a project folder but should not have access to a subfolder. Permissions in Octaved Flow are additive. So if the user receives permissions via another source, for example via the assignment as Responsible or via a project role, then these apply and the None permission role does not override them.