Organizations
An org is a container for shared libraries, members, groups, and an audit log. Created on the Teams plan, run from the org page, separate from your personal library.
An organization in sweetdocs is the workspace shape for teams. It owns its own libraries, has a member list with roles, supports access groups, and tracks an audit log of everything that happens inside it. Personal libraries continue to exist alongside the org — you can belong to multiple orgs without losing your personal workspace.
Acme Engineering
- Architecture12 members
- Onboarding5 members
- Design reviews3 members
- LLee VaniderstineOwner
- SSam ParkAdmin
- AAvery ChenMember
- Engineering8 members
- Design3 members
- Leadership4 members
What an org is
In the database, an organization is a row in organizations:
| Field | Meaning |
|---|---|
id | UUID |
name | The org’s display name |
owner_id | The user who currently owns the org |
sharing_mode | members, domain, or open — controls how invitations are allowed |
domain_whitelist | Array of email domains (for domain sharing mode) |
created_at | When it was created |
The org is the container for team libraries, members, and groups.
Creating an org
The org page lives at /app/org/:id and is created during the Teams plan upgrade flow:
- Upgrade to Teams from Pricing or Plans
- The upgrade flow asks for a workspace name
- Sweetdocs creates the org row and adds you as Owner
- You’re redirected to the org’s page
An individual user can belong to multiple orgs simultaneously — useful when you consult or freelance with several teams. Each org’s libraries appear in the library switcher alongside your personal library.
What lives inside an org
| Resource | Notes |
|---|---|
| Libraries | One or more, each holding its own folder tree and documents — see Team libraries |
| Members | Users who can access the org’s libraries, with roles — see Org members + roles |
| Groups | Reusable membership sets for ACL grants — see Groups |
| Invites | Pending email invitations (target_type = ‘org’ for org-level joins) |
| Audit log | Timeline of every action by every member, scoped to this org — see Audit log |
Sharing modes
The sharing_mode field controls how invitations are handled:
| Mode | Behavior |
|---|---|
members (default) | Only org Owners and Admins can invite. Each invite is per-person. |
domain | Anyone signing up with an email from a domain in domain_whitelist automatically joins as a Member — see Domain capture |
open | Anyone can request access (used rarely; mostly for very public communities) |
Changing the sharing mode requires Owner or Admin access.
Plan requirement
Organizations are a Teams plan feature. Pro plans get one personal library and no orgs; Teams plans get one org with one or more libraries plus a per-seat billing model. See Plans for the full breakdown.
What’s not in v1
| Missing | Notes |
|---|---|
| Multiple orgs per Teams subscription | One org per subscription; multiple orgs require separate subscriptions |
| Org branding (custom logo, custom theme defaults) | Not configurable in v1 |
| Inter-org document linking | Not modeled — docs belong to one library in one org |
| Org-level Recycling Bin (separate from per-user bin) | Not in v1 — the Recycling Bin is per-user, even for org content |