# Feature OP-14680 - [API] Write access for project storage collection

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

## 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 | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Found in mobile app version |  |
| Follow-up feedback e-mail |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable | Eric Schubert |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** a developer of a consumer app  
**I want to** configure project-specific storage locations via REST v3 API  
**so that** a script / tool can set up new projects in OpenProject and Nextcloud and combine those without manual user interaction.

For the use case of the requesting stakeholder, the "automatically managed NC folders" option for the file storage plugin is not sufficient, as the script / tool has to pre-configure the new NC folders with a certain default structure (subfolders, semi-public share links and default README files etc.).

Builds upon the read access to project\_storages already implemented in <mention class="mention" data-id="50234" data-type="work_package" data-text="#50234">\#50234</mention> 

**Acceptance criteria**

  - Add CREATE request via `POST /api/v3/project_storages` such that the script / tool can decide about the Nextcloud path
  - The implementation can take it as given that OIDC is already homogeneously configured in both OP and NC via feature <mention class="mention" data-id="52828" data-type="work_package" data-text="#52828">#52828</mention>