Organizations
Organizations let multiple people work together in post.buzz. A member of an org can be granted access to shared social accounts, collaborate on content, and see shared activity — while billing stays personal to each user.
How orgs work
- Each user can belong to multiple organizations (up to 5).
- An organization has members with roles: owner, admin, member.
- The org owns the workspace; members act within it.
Billing is personal, not organizational. Each user manages their own plan and credits. An org doesn't have its own subscription — members bring their own. (See ADR-004 in the codebase for the rationale.)
Shared accounts
Social accounts can be shared with teammates through account membership. When an account is shared, the members you grant access to can publish, engage, and view analytics for it, subject to their role. This is how an agency or team operates many channels together without sharing credentials.
Access is scoped per account, so you can share some channels widely and keep others private.
Roles
| Role | Can do |
|---|---|
| Owner | Everything, including managing the org and its members. |
| Admin | Manage content and members' access to accounts. |
| Member | Work on accounts they've been granted access to. |
Activity and audit
Shared workspaces benefit from visibility. The activity feed records notable actions across the workspace so team members can see who did what — useful for coordination and review.
API access
API keys are scoped to a user, not an org. A key can act on any account the key's user can access — including accounts shared via org membership. To give an integration access to team channels, share those accounts with the user whose key the integration uses.