buddyboss/manage-folder manages the folders that hold documents.
Folders nest, and that nesting has two consequences that both cascade.
At a glance
| Ability | buddyboss/manage-folder |
| Toolset | BuddyBoss — toolset/buddyboss |
| Group | BuddyBoss › Media & Documents |
| Requires | AcrossAI Pro, plus BuddyBoss Platform active on the site |
| Capability | manage_options |
| Safety | Writes data |
| Repeatable | Idempotent — running it twice leaves the same result |
| Ships in | AcrossAI Pro 0.9.16 and later |
Privacy and deletion both cascade
Folders nest and push their privacy and group down to everything inside them, so setting a folder to public can expose every document beneath it in one call — including documents in sub-folders this request never mentions. The delete action removes the folder and its entire subtree, and confirm_item_count must match the total number of documents and sub-folders underneath, not just the direct children.
How it works
The first is privacy. A folder pushes its privacy and group down to everything inside it, at every level. Setting a folder to public exposes every document beneath it — including documents in sub-folders that were never mentioned and whose own privacy said otherwise.
That is a single call that can change access to hundreds of files, and nothing in the request describes the scope.
The second is deletion. Deleting a folder removes its entire subtree, and confirm_item_count must match the total number of documents and sub-folders underneath — not just the direct children.
Using the total rather than the direct count is the whole point: a folder with two direct children and ninety files three levels down is a deletion nobody would authorise if they knew, and the count is how they find out.
Albums for photos and videos are flat and handled by buddyboss/manage-album. The absence of nesting is why that one is simpler.
Idempotent for the non-delete actions.
Input
| Name | Type | Required | What it is |
|---|---|---|---|
action | string | Yes | list, create, update or delete. |
folder_id | integer | For update and delete | Which folder. |
title | string | For create | The folder title. |
parent_id | integer | No | Nest under this folder. |
privacy | string | No | Folder privacy. Propagates down the entire subtree. |
group_id | integer | No | Work with a group’s folders. |
confirm_item_count | integer | For delete | The total documents and sub-folders underneath, at every level. |
confirm | boolean | Yes — must be true | The irreversibility gate. Without it the call is refused before anything is touched. |
What comes back
| Name | Type | What it is |
|---|---|---|
folder | object | The folder after the write. |
items_deleted | integer | How much of the subtree went, on delete. |
success | boolean | Whether the call completed. |
message | string | A one-line summary of what happened, suitable for showing a human. |
error_code | string | Present only on failure — a stable machine-readable reason, such as a missing field, a wrong field type or an unmet confirmation. |
Example
Ask your assistant:
Make the handbook folder visible to everyone.
It resolves to one call:
{
"ability": "buddyboss/manage-folder",
"parameters": {
"action": "update",
"folder_id": 22,
"privacy": "public"
}
}Worth knowing
- Privacy propagates through the whole subtree, including sub-folders you did not name.
- Deletion takes the entire subtree.
- The confirmation count is the total, not the direct children.
- Albums are flat and do none of this.
Related abilities
- BuddyBoss Manage Document — move documents between folders
- BuddyBoss Manage Album — the flat equivalent
Get the plugins:
AcrossAI Abilities Manager · AcrossAI MCP Manager
Browse the rest: Every ability, by category