# Epic ITSM-58 - Guest users

Project: Stream IT service management (ITSM)
Status: new
URL: https://community.openproject.org/work_packages/ITSM-58

## Detailed specification

### Motivation and background information

Guest users

*   Could open service desk tickets or be approvers on them
    
*   Could be assigned assets (e.g. laptop)
    
*   Could be invited to participate on single work packages
    

Having a concept of guest users is a prerequisite of implementing all of these. Through this permission, OpenProject administrators are flexible in their assignment of permissions and can use SCIM or OIDC to provision licenses for users as needed.

### Acceptance criteria

*   A new permission named `Use OpenProject` should exist as a global permission
    
*   Users without this permission should not be assignable to any other global or project-scoped permission
    
*   Users without this permission should not count towards enterprise usage
    
*   Users without this permission should not be invitable to a project unless they receive this permission
    
*   Users without this permission should see only public resources in OpenProject
    
*   Users without this permission should not be able to create API access tokens
    
*   The OpenProject API must expose the user&#x27;s last log-in time for the option of an automated license cleanup

### Out of scope

  - Users without the `Use OpenProject` permission should be able to use the service portal (<mention class="mention" data-id="82451" data-type="work_package" data-text="###ITSM-48" data-display-id="ITSM-48">\#\#\#ITSM-48</mention>)

  - Users without the `Use OpenProject` permission should be able to get assets assigned once asset management is implemented

  - Work packages should be sharable with users without the `Use OpenProject` permission *(future implementation)*

  - An invite flow that automatically grants license usage *(future implementation)*

  - Automatically revoking a license if a user has not logged in for X days *(this can be done using external tools through the API)*

| Attribute | Value |
| --- | --- |
| Mockups |  |

## Planning

| Attribute | Value |
| --- | --- |
| Roadmap | 2027 Q1 |
| Date |  |
| Votes |  |
| List |  |
| Target versions |  |
| Relevance |  |

## Subitems

_No work packages_

## Bugs and other work packages

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Enterprise plan |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager | Nova Bonic |
| Feature Lead |  |
| Designer | Marc Alcobé |
| Developers |  |
| Requested by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| Work |  |

## Description

As an **OpenProject administrator**  
I need to be able to **create guest users**  
So that they do not use OpenProject license seats and can **only access limited functions**.

<br>

Guest users should not trigger additional license costs and are only able to use a 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 be granted to this user unless they also hold the `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 license usage, so we only count as enterprise seats the users holding `Use OpenProject` permission.
