Libraries
The top-level container in sweetdocs. Every user has one personal library; organizations can host any number of org libraries. Folders and documents live inside a library.
A library is the top-level container. It holds folders, folders hold other folders and documents — and documents are the leaves. Every user has one personal library; if you belong to an organization, the organization can host one or more org libraries that you access alongside your personal one.
What lives in a library
A library is a row in the libraries table with:
id— UUIDname— the library’s display nameorg_id— null for a personal library, the org’s UUID for an org libraryowner_id— the user who owns it (for personal libraries)sharing_mode— controls how invites/sharing behave inside the library
Inside the library, you have:
- Folders — see Folders
- Documents — every doc has a
library_idpointing back at its library
Documents and folders are scoped to one library. A document doesn’t exist in multiple libraries; if you need it in two places, copy it.
Two flavors
| Library type | What it is | Permissions baseline |
|---|---|---|
| Personal | Auto-created at sign-up; one per user; org_id IS NULL | The owner has automatic Manage; everyone else needs explicit ACL grants |
| Org | Created by an org Owner or Admin within an organization; lives inside that org | Org Owners and Admins get automatic Manage; everyone else needs explicit ACL grants |
The difference matters for permissions: in an org library the library owner_id doesn’t grant anything; only org-level roles (Owner / Admin) do. See Permissions for the full resolution rules.
Personal library
Created automatically the first time you sign up. Its default name is My Documents (you can rename it). It’s bound to your user account, can’t be transferred to anyone else, and lives entirely outside any organization.
It’s the only library that exists when you’re not in an organization. All your private docs live here.
Org library
Created inside an organization. Org libraries are the main work surface for teams — see Team libraries for the team workflow and Organizations for the org-level model.
You can belong to multiple organizations and see all of their libraries from one workspace.
Switching between libraries
Each library has its own sidebar tree, its own pin set, and its own active context. The library switcher at the top of the sidebar shows which library you’re currently viewing.
To switch:
- Click the library switcher → pick a library
- Or navigate to a doc that lives in a different library (the sidebar follows the doc)
The active library affects:
- Which folder tree the sidebar shows
- Which pins are surfaced in the Pinned section (pins are per-user, per-library — see Pinning)
- Which library new documents are created in (defaults to the active library)
Search and cross-library views
Search operates across all libraries you have access to — you don’t need to switch libraries to find a doc. Results show the library name next to each hit so you know where the doc lives.
The Recycling Bin (per-user) and Shared with me (per-user) views also cross library boundaries.
What a library doesn’t do
| Not | Notes |
|---|---|
| Hold itself in a tree | Libraries don’t nest. Folders nest inside a library; libraries are flat at the top. |
| Have its own public link | Public links are document-only. |
| Carry plan-level features | Plans attach to users (and orgs); libraries inherit. |
| Get exported as a single archive | Export is per-document in v1. |