Permission |
Global |
Previous permission, changed or added |
Explanation |
Ticket |
Create projects |
✅ |
Previous (unchanged) |
Allows the creation of workspace of the type "project" |
|
Create programs |
✅ |
Added |
Allows the creation of workspace of the type "program" |
|
Create portfolio |
✅ |
Added |
Allows the creation of workspace of the type "portfolio" |
|
|
|
|
The |
|
|
|
|
The |
|
|
|
|
The |
|
Manage templates |
✅ |
Added |
Allows turning a workspace into a template and removing the workspace from the set of templates. Potentially, this also needs to be separated into three different permissions, one per workspace type. Adding this permission might be out of scope as it is not strictly necessary for the epic. |
|
Copy workspace |
Replaces "Copy projects" The dependency on both "edit project" as well as "manage members" is added. |
Users will need any of "Create projects", "Create programs" or "Create portfolio" to actually copy a workspace. That way, the creation of projects is more tightly controlled. On the other hand, this might be complicated for users to understand. |
||
Create subprojects |
Removed |
|||
Select parent |
Has a dependency on "edit project". |
The permission allows selecting the parent workspace to the workspace the permission is granted in. It no longer allows the creation of new workspaces. |
||
Edit workspace |
"Edit project" permission is renamed and changed |
Looses ability to select parent |
Use case |
Required global permissions |
Required project permissions |
Remarks |
Add a project (without hierarchy) |
Create projects |
||
Add a program (without hierarchy) |
Create programs |
||
Add a portfolio (without hierarchy |
Create portfolios |
||
Turn a workspace (e.g project) into a child of another workspace (e.g. portfolio) |
"Select parent" in the child project. Any permission in the parent project (for visibility). |
This action could be triggered from the child (current state) or from the parent or from both. |
|
Create a workspace (e.g project) as a child of another workspace (e.g. portfolio) |
Create projects/programs |
"Select parent" in the newly created project. Any permission in the parent project (for visibility) |
This is the combination of the permission specifications above. E.g. if a user has both the "Create projects" permission as well as "Select parent" as the newly created project admin, a new project can be created with the portfolio as its parent right away. Create portfolio is not listed as a required global permission as a portfolio cannot be a child. The "Create subproject" button in the project administration is only displayed if the role the user will receive in a newly created workspace has the "Select parent" permission. |
Copy a workspace (not a template) |
create projects/portfolios/programs |
"Copy workspace" in the workspace to be copied. |
Workspaces in which the user has "Copy workspace" permission can be copied. Templates cannot be copied by that permission, it requires "Create XYZ from template". |
Copy a project template |
Create project from templates |
Projects marked as template are completely copyable. It also does not require the "Copy workspace" permission in the copied template project. |
|
Copy a program template |
Create program from templates |
Programs marked as template are completely copyable. It also does not require the "Copy workspace" permission in the copied template program. |
|
Copy a portfolio template |
Create project from templates |
Portfolios marked as template are completely copyable. It also does not require the "Copy workspace" permission in the copied template portfolio. |
|
Turn a workspace into a template |
Manage templates |
Any permission in the project. |
From This is risky as it allows privilege escalation. A user might first turn a workspace into a template, then copy it to potentially gain access to information previously not accessible to them. |
Remove a workspace from the set of templates |
Manage templates |
Any permission in the project. |
From |