Content
View differences
Updated by Niels Lindenthal 3 days ago
As an **OpenProject administrator**
I need to give users access be able to the helpdesk module only
**create guest users**
So that I can they do not use an existing OpenProject installation for ITSM purposes. license seats and can **only access limited functions**.
**Acceptance criteria** <br>
* There is Guest users should not trigger additional license costs and are only able to use a global permission `Access helpdesk module`.
* Only users with limited set of functions such as the help desk, assigning assets, or sharing single work packages.
In order to ensure that the [user lifecycle](https://www.openproject.org/docs/user-guide/projects/project-home/project-life-cycle/) stays manageable and provisioning via SCIM stays relatively simple, this should be done as a **permission** rather than a new kind of user.
**All other permissions** should be parented to the `Use OpenProject` permission _(naming subject to change)_, such that no permission can access be granted to this user unless they also hold the helpdesk module.
* All users that can `Use OpenProject` permission. Users without this permission should only be able to access public resources and should not be invitable to a project.
This permission also drives the helpdesk module need a license usage, so we only count as enterprise subscription.
**Out of scope**
* A concept for guest seats the users -> separate feature
* Anonyous users -> separate feature holding `Use OpenProject` permission.
**Acceptance criteria**
* There is
* Only users with
In order to ensure that the [user lifecycle](https://www.openproject.org/docs/user-guide/projects/project-home/project-life-cycle/) stays manageable and provisioning via SCIM stays relatively simple,
**All other permissions** should be parented to the `Use OpenProject`
* All users that can
This permission also drives
**Out of scope**
* A concept for guest
* Anonyous users -> separate feature