Organizations, Workspaces, and Permissions

A workspace keeps one brand or client's connected social accounts, posts, and publishing calendar together. A team seat is a person invited to collaborate. Keeping each client in its own workspace helps your team choose the right accounts and keeps client access separate.

Workspace, team seat, or social account?

Does each team member get separate limits?

No. Social-account capacity is shared across the plan owner's workspaces. Adding a person does not add social-account slots or give them a separate copy of the plan. Seats determine how many people can collaborate; workspace access and roles determine what each person can do.

Social accounts are not automatically divided equally between team members. You choose which accounts to connect in each workspace and who can work there. Several teammates can work on the same connected accounts within their permissions. A seat does not reserve a fixed share of the allowance.

Example: 500 social accounts, 200 seats, and 200 workspaces

These are three separate capacities. Ten client workspaces with five social accounts each use 50 of the 500 social-account slots and ten of the 200 workspaces. Invite collaborators to the relevant workspaces and choose their roles. Each person does not receive another 500 social-account slots.

This is an illustrative example, not a plan offer. Check the plan owner's billing page for the actual allowances. You do not need to use every seat or workspace, and creating another workspace does not increase the account's total social-account allowance.

Can invited members see other clients or billing?

Admin and Editor access follows assigned workspaces and permissions. Owner grants full access to the invited account, including billing and all its workspaces. Choose Admin or Editor for someone who should work only in selected workspaces. Review the team-role guide before granting access.

If an invited member buys their own subscription, it does not increase your shared workspace's allowances. That workspace continues to use its owner's plan; the member's own workspaces use their own account's plan.

Start with one workspace

1. Create or choose one workspace for your business or first client, and confirm its timezone.
2. Connect one social account in that workspace.
3. Invite only the people who need access, reviewing roles and selected workspaces before sending.
4. Prepare and review a draft, then schedule or publish it.
5. Check the publishing result for each destination. A scheduled post is not yet a confirmed publication.

Add more workspaces, connected accounts, and people as needed within your plan. Follow the Postly Starter Pack for the full first-post checklist.

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

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.

• Team Roles and CRM Access
• CRM Channels, Limits, and Workspace Access