Organizations, Workspaces, and Permissions
Good Postly structure makes everything else easier. Workspaces are not just folders. They are the operating boundary for destinations, campaigns, approvals, analytics, and access.
How to think about structure
Organization
Use organizations for the broader business or umbrella entity.
Workspace
Use workspaces for the operating unit that should own:
- connected destinations
- campaigns
- approvals
- analytics context
- team access
Common workspace models include:
- one workspace per client
- one workspace per brand
- one workspace per region or business unit
Why permissions matter
Permissions decide who can:
- connect destinations
- create or edit drafts
- approve posts
- publish directly
- review results
If publishing is sensitive, keep the creator and approver roles separate.
Signs your structure is working
- channels are easy to find
- campaigns do not cross the wrong clients or brands
- reviewers know what belongs to them
- analytics reads like one coherent story
Signs you should restructure
- too many unrelated destinations live together
- client approvals are getting mixed up
- reporting is hard to separate
- teams are worried about publishing to the wrong account
For API and MCP, workspace-first design is especially important. The safest integrations always resolve the workspace before listing targets or creating posts.