Team libraries

Org-owned libraries: a shared workspace where the folder tree is the same for everyone, permissions follow org and group roles, and new docs default to org-visible.

A team library is a library owned by an organization rather than a single user. The folder tree, documents, and pin-vs-shared model all work the same way they do in a personal library — but the permission baseline is different, and the library is shared by every org member who has access.

Creating a team library

Team libraries are created from inside an organization, by org Owners and Admins:

1. Open the org page (/app/org/:id — also accessible via the sidebar’s org switcher)
2. Libraries section → New library
3. Name the library

The library inherits the org’s org_id and becomes visible to org members.

Who can see a team library

Visibility is driven by the permissions resolver:

• Org Owners and Admins see and have Manage on every library in the org automatically
• Org Members see libraries they’ve been granted access to via the library’s ACL
• Within a library, folder-level and document-level ACL grants further refine access (including restricted folders)

The library doesn’t have a “members” list of its own — it has an ACL like any other resource. Adding a person or group to the library’s ACL at the Read or Write level grants standing access to the library’s contents.

Org Members ≠ automatic access

This is the key difference from personal libraries: in an org library, the personal “owner has Manage” shortcut doesn’t apply. New org members start with no access to org libraries until:

• They’re added to the library’s ACL directly
• They’re added to a group that’s on the library’s ACL
• They’re upgraded to org Admin or Owner

This is least-privilege by default — preferable to “joined the org, can see everything.”

Shared folder structure

The folder tree is the same for everyone with access to the library. When someone creates a folder, renames one, moves a document, or restructures the tree, every other member with access sees the change in realtime (via the same realtime subscription that powers the personal library).

There’s no per-user view, no personal folder organization that diverges from the shared one. If you want personal organization, use Pinning — pins are per-user and don’t affect anyone else.

Restricted folders for private subtrees

A folder inside a team library can be marked restricted, which cuts the permission inheritance chain — see Folders and Permissions for the details.

Use this for HR docs, compensation reviews, or strategy drafts that should be isolated to a few people even within an otherwise open org library.

Groups

Groups are reusable membership sets — “Engineering”, “Product”, “Leadership”, etc. When you add a group to a library or folder ACL, every group member inherits the grant; adding a person to the group later automatically extends the grant.

This is the recommended way to manage team-library access at scale: structure your access by group, not by individual.

Audit log

Every change to a team library — folder creates, document creates, sharing changes, restores, etc. — flows through the audit log. Org Admins can review the timeline; see Audit log.

Plan availability

Team libraries are an organization feature. See Plans for which plans include organizations and how seat counts work.

Switching context

Org libraries appear alongside your personal library in the sidebar’s library switcher. Picking one swaps the sidebar tree, the Pinned section, the active context for new documents, and the document list filters — without affecting Search, which always covers every library you can access.