Organizations
The organization is post.buzz's top-level container: it owns the teams, social accounts, and subscriptions. Every user gets a personal organization at signup (named after you), which is what most creators ever need. Agencies and companies can run additional organizations — or keep client brands as teams inside one org.
How orgs work
- Each user can create organizations; your plan's workspaces quota caps how many you own (1 on Starter, up to 25 on Agency — see plans).
- An organization has members with roles: owner, admin, member.
- Members are invited by email and can be managed from the org settings; your plan's members (seats) quota caps members plus pending invites.
Subscriptions belong to an organization. For a personal org that looks identical to "billing is mine" — the org is you. If you operate multiple orgs, each carries its own plan, and deleting an org cancels its subscriptions first.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including renaming/deleting the org, billing, and members. |
| Admin | Manage content, members, and account access. |
| Member | Work on accounts they've been granted access to. |
Shared accounts
Within an organization, every member works on the same teams and social accounts — membership is the access grant. (There are no per-account sharing rows across orgs.) An agency keeps each client in its own org when isolation matters, or in separate teams when it doesn't.
Renaming and deleting
From Settings → Organization: rename the org (the slug is fixed), review
members, or — in the danger zone — delete the workspace by typing DELETE.
Deletion signs you out and removes the org's teams and accounts; subscriptions
are cancelled server-side as part of it, but review billing first so nothing
bills in the gap.
API access
API keys belong to an organization and act on everything in it. To scope an integration narrowly, create its key in an org that only holds the channels the integration may touch.