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
Switch workspaces
Open the workspace picker from the workspace name at the top of the navigation. Find the workspace you want, then select Switch workspace beneath its name. The workspace you are already using is labeled Current workspace. You can also select a workspace by clicking its name.
Switching changes the workspace used for connected channels, publishing and results. Check the workspace name before creating content for another client or brand. The checkboxes in the picker select workspaces for management actions; they do not switch your active workspace.
Workspace settings and profile
Open a workspace's menu and select Settings, then Workspace settings to manage its name, logo, ID and profile together. The optional workspace profile describes whether the workspace is for an individual, business, agency or enterprise. Choose Use organization default to inherit the organization's profile. This does not change pricing or permissions.
Why permissions matter
Permissions decide who can:
- connect destinations
- create or edit drafts
- approve posts
- publish directly
- review results
If publishing is sensitive, separate content creation and approval permissions through your approval workflow.
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.
Good next guides
- Connect Social Accounts and Destinations
- Share Connection Links with Clients
- Approval Workflow
- API Workflows
Team roles and CRM restrictions
Select Owner, Admin, and Editor roles with checkboxes during invitations and role updates. Owner grants full account access, including billing and all workspaces. No role is preselected, and there is no additional CRM role to assign. CRM access follows workspace membership, permissions, owner restrictions, and plan access.
CRM is allowed in organizations and workspaces by default. Only the account Owner can block it under CRM settings > Workspace access. Owners and Admins can select compatible channels under CRM settings > CRM channels within their permitted workspaces. There is no separate CRM role. CRM capacity is account-wide, and Publishing and CRM activation are independent even when they share provider authorization.