# Feature OP-9672 - New "read only" scope for OAuth2

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-9672

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module |  |
| Feature Flag |  |
| Requires doc change | Yes |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

**As** an administrator integrating two systems such as OpenProject and Nextcloud through OpenProject's OAuth2 apps  
**I want to** have the option to scope the token's access rights to *read only*  
**so that** the overall risk of leaking API tokens that can edit data is reduced.

**Acceptance criteria**

  - When setting up a OAuth2 app in OpenProject the admin can chose scopes *read only* and *read and write* for the API V3.
  - When the scope is *read only* then created tokens should not be allowed to modify any data whatsoever on OpenProject

I don't know how what to set for the RICE score here.
