---
title: "Update organization-level folder permissions"
method: PUT
path: "/v1/folders/{folderId}/permissions"
tags: ["Folder permissions"]
---

# Update organization-level folder permissions

`PUT /v1/folders/{folderId}/permissions`

## Request

- Base URL: `https://blobsrus.omniapp.co/api`
- URL: `https://blobsrus.omniapp.co/api/v1/folders/{folderId}/permissions`
- Auth: HTTP bearer

Set the role every member of the organization holds on a folder, and/or turn [AccessBoost](/share#boosting-permissions-with-accessboost) on or off for that organization-wide access, without naming individual users or groups. The role cascades to every descendant folder and document, so a single call can re-permission an entire folder tree.

At least one of `organizationRole` or `organizationAccessBoost` is required.

## Path parameters

- `folderId` string, uuid, required

## Request body

- object
  - `organizationAccessBoost` boolean: Whether everyone in the organization gets [AccessBoost](/share#boosting-permissions-with-accessboost) on this folder. Setting this to `true` requires an organization role that grants access, either sent in the same request or already on the folder; otherwise the request is rejected.
  - `organizationRole` 'NO_ACCESS' | 'VIEWER' | 'EDITOR' | 'MANAGER' | 'OWNER': The role every member of the organization holds on the folder. Must be one of `NO_ACCESS`, `VIEWER`, `EDITOR`, or `MANAGER`. `OWNER` cannot be granted at the organization level. Pass `null` to clear the organization role.

## Response `200`

Permission settings updated successfully

- object
  - `success` boolean, required: Whether the permission settings were updated successfully

## Other responses

- `400`: Bad Request Possible causes: - Neither `organizationRole` nor `organizationAccessBoost` was provided, or an unrecognized field was included - `organizationRole` was set to `OWNER`, which cannot be granted at the organization level - `organizationAccessBoost: true` was combined with a role that grants no access — either the one in the request, or the folder's current role when the request omits `organizationRole`
- `403`: Forbidden Possible causes: - `User does not have permission to manage folder permissions` - The user sending the API request must have **Manager** permissions for the folder. - AccessBoost is turned off for the organization - A user-scoped key lacks boost provisioning - The organization's **Organization access for personal content** setting is off, the folder is in a personal space (My Documents), and `organizationRole` would raise the Organization role above what the folder already holds, directly or from a parent folder. The error message is `Your organization does not allow sharing personal content with the whole organization. Move it to a shared space first.`
- `404`: Not Found Possible error messages: - `Folder with identifier "<folderId>" not found`
- `429`: Too Many Requests - Rate limit exceeded (60 requests/minute)

## Changes

- **2026-11-03** `43290040f88f`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/omni/apis/omni-api/changes/v1/folders/:folderId/permissions/put.md)

---

[API](https://skmtc.dev/omni/apis/omni-api.md) - [All operations](https://skmtc.dev/omni/apis/omni-api/llms.txt) - [OpenAPI document](https://skmtc.dev/omni/apis/omni-api/revisions/43290040f88f?raw)