Workspace Permissions
From Projectivity Documentation
The permissions the user has in a workspace depend on his/her access level.
Each user has an unique, well-defined access level in each workspace. The following table lists the available access levels:
| Access Level | Description |
|---|---|
| Owner | This is the most powerful access level. If you have this access level in a workspace you are able to do everything. |
| Trusted | This is the access level of a user who can access public documents. It is the access level used to spread knowledge across the company; when a user is trusted on a workspace, he can access all the public documentation that is associated to it and children workspaces.
However this access level does not allow to access the workspaces below the projects. In order to go below the user needs to be Member at least. |
| Active | This is the access level of a user who is supposed to write documentation in the workspace.
Note: as an exception to the general law, this access level is not inherited on children workspaces by the user. |
| Member | This is the default access level when a user is assigned to a project. In terms of rights it is equivalent to Trusted but allows the user to access children workspaces. |
| Customer | This access level is used to give the customer of a project access to it. It gives a limited access to the project. |
| External | This is the weakest access level. The user with this access level cannot access the workspace at all neither he/she can access the associated documents. You give a user the external access level if you want to be sure he/she cannot access the workspace and the documents in it. |
Access Levels are inherited across the workspace hierarchy. Giving an access level to a resource in a workspace, gives him/her the same access level on sub-workspaces (with the exception of Active Access Level that is not inherited).
For instance, the following Figure shows some assignments of a resource in a hierarchy of workspaces.
Given the access level inheritance rule, the resulting access levels of the resource are:
| workspace | access level | access level assignment |
|---|---|---|
| 1 | trusted | explicit assignment |
| 1.1 | owner | explicit assignment |
| 1.1.1 | owner | inherited from 1.1 |
| 1.1.2 | owner | inherited from 1.1 |
| 1.1.2 | owner | inherited from 1.1 |
| 1.2 | active | explicit assignment |
| 1.2.1 | trusted | inherited from 1
active on 1.2 is not inherited |
| 1.2.2 | member | explicit assignment |
The following table defines the permissions corresponding to each kind of workspace.
| Structural | Project | Dynamic and
Folder | |
|---|---|---|---|
| Owner | access
manage | access
manage | access
manage |
| Active | access | access | access |
| Trusted | access | access | none |
| Member | n.a. | access | n.a. |
| Customer | n.a. | access | n.a. |
| External | none | none | none |
The following table gives more detail on permissions:
| Access | Manage | |
|---|---|---|
| The user is allowed to |
|
NOTE: the user is able to assign resources that he/her owns, i.e. resources that are already assigned to a workspace he/she owns |
