Folders
Folders
Folders are where documents and outlines live, and what sharing hangs off: share a folder once instead of every file inside it. A folder can be shared with a person, a team or everyone here, or put on a public link.
In the sidebar under Files → Folders. Needs: nothing else switched on. What goes inside folders comes from Documents and Outlines.
Folders screen
The screen lists folders, ten at a time, loading more as you scroll. Each row shows:
- Folder: its name, with the folders above it in small print when it is nested.
- Depth: how deep it sits.
- Shared: "link" when it is on a public link, otherwise "private".
- Updated: when it last changed.
With permission to change folders, each row has Edit (to rename it) and Delete, and the screen has New folder. On a folder you made, or on any folder if you are an administrator, there is also Share. With no folders yet, it says "No folders".
Shared with me, below the list, holds the folders, documents and outlines somebody shared with you. Each says how it reaches you: with you, through a team you are in, or with everyone.
Everyone who can open Folders sees the workspace's folder list. Sharing decides who can open the documents and outlines inside. A folder can be filed under a project, and is then listed on that project's home page.
Create a folder
- Press New folder.
- Type a Name, such as "Contracts". You can also pick the Project it belongs to.
- Press Create. The folder is made at the top level. To make one inside another, or to move one, use the agent tools.
Rename a folder
Press Edit on its row, change the Name and save. Only the name changes: what it holds, where it sits and who it is shared with stay the same.
Share a folder
- Press Share on the folder's row.
- See who has it now. Add a person, a team or everyone here, to read or to edit.
- Take a share away from the same place.
A share on a folder reaches everything beneath it.
Delete a folder
Press Delete on its row and confirm. Every folder inside it goes too. Documents and outlines filed in them are not deleted: they are left without a folder.
Request, public link and copy
These are done through the agent tools:
- Ask for access to something you cannot open. The request waits for its owner, who approves it (as viewer unless editor was asked for) or declines it. The person who asked is told if it is declined.
- Public link: put a folder and everything beneath it on a link anyone holding it can read, signed in or not, at
https://<your-deployment>/share/folders/<token>. Turning the link off clears it for good; turning it on again issues a new one. - Duplicate a document, an outline or a whole folder beside the original. Only what you can see is copied.
- Add to my files: keep your own copy of something shared with you.
Who can do what
| Permission | Label | Lets you |
|---|---|---|
folders:read | View folders | Open Folders, see what is shared with you and, for what you own, who it is shared with, ask for access, and copy shared things into your own files |
folders:write | Create, rename and move folders | Create, rename, move, duplicate and delete folders, share and unshare, approve or decline requests, and turn public links on and off |
On top of the permission, sharing, approving requests and public links are for the owner (for a folder, whoever made it) or an administrator. Anyone may give up their own access. See People, roles and permissions.
What happens on its own
Nothing in this module runs on a schedule.
What agents can do
Agents can organise folders and handle access requests. Changes go through your approval rules. Deleting a folder and turning off a public link cannot be undone. Approving a request and making a public link open things to people, so under the default approval policy a person is asked first. Sharing, approving and public links are refused through an API key. See Agents and approvals.
Read only: folders.list, folders.tree, folders.sharedWithMe, folders.shares, folders.myRequests, folders.incomingRequests
Organise: folders.create, folders.rename, folders.move, folders.duplicate, folders.addToMyFiles, folders.remove (cannot be undone)
Share and requests: folders.share, folders.unshare, folders.requestAccess, folders.denyRequest, folders.approveRequest (asks first), folders.sharePublic (asks first), folders.unsharePublic (cannot be undone)
folders.addToMyFiles and folders.requestAccess need a key that acts for a person, because a copy or a request belongs to someone.
Over MCP the same tools are named folders__list, folders__share and so on. See API keys and MCP access.