What’s new in version 6.0007
Key point: Project roles, notifications and permissions.

Project roles and notifications

We’ve clarified the project roles in the user interface. From this version, the default role for projects is contributor, and the default notification setting is set to normal.

The notifications settings are not used in projects because you cannot create documents, comments or any other item that would send a notification. 

The possible roles in project are now:

  • Contributor
  • Manager
  • Moderator

Existing projects and project members are not affected, but if they have a legacy role such as “reviewer”, a warning icon is displayed next to it.

Why the change?

For security, there is no need to provide more permissions than are required, so we’ve simplified the roles in projects and removed the following roles from options:

  • Guest – any member of a group has automatic guest access to the parent project, so this role isn’t necessary, and if a member is removed from the group, they should no longer have access to the parent project.
  • Reviewer – in a project, a reviewer is simply a guest who can see the list of other members, so in the absence of documents and comments, it is not a useful role.
  • Approver – without workflows or comments, this role is effectively identical to the role of manager.
  • Approver and moderator – for the same reason, this role is effectively identical to the role of moderator.

Project contributors

Project contributors have a limited role compared to project managers, but they can create groups. We’ve added a link for project contributors to create a new group directly from the navigation menu.