Skip to content

Team Operations

Agency Client Onboarding: Workspaces, Channels, Approvals and Reports

Onboard a social media agency client with separate workspaces, shared channel capacity, appropriate permissions, content approvals, and a reporting routine.

Give each client a clear place for their content, a named reviewer, and a reliable way to see what was published. This guide follows a practical example: an agency bringing four clients onto Postly, each with five publishing destinations. That uses 20 channels across the plan owner's workspaces. It does not create four separate channel allowances.

1. Agree on the destinations and responsibilities

List the pages, profiles, blogs, or other destinations you will manage before connecting them. A Facebook Page and its linked Instagram account are two publishing destinations. Record who owns each account, who can authorize access, who prepares content, and who approves it.

Use Compare plans to check the features and separate subscriptions you need. Pro offers flexible channel quantities. The 5, 20, 50, 100, and 500 choices are shortcuts; you can enter a supported custom quantity. If you need 20 now and four more later, review a change to 24 in Billing. Review the displayed price and terms before confirming.

Free has 50 one-time publishes across the account. Each publishing destination counts separately, so a post sent to five destinations uses five publishes. It is useful for trying the workflow, but is not an ongoing monthly publishing allowance. Existing lifetime or legacy purchases retain their own entitlements.

2. Create a workspace for the client

Use a recognizable client name and check the workspace before connecting channels or creating content. Organizations group workspaces; workspaces separate the client's operational context. See Organizations, Workspaces, and Permissions.

Invite your team and the client's reviewers to the relevant workspace with the permissions they need. Owner grants full account access, including billing and all workspaces. Use appropriate Admin or Editor permissions for someone who should work only on one client's brand. An invitation does not buy additional channel capacity. Review the team role guide before granting access.

3. Let the client authorize their channels

Prepare a supported private connection link when someone else needs to authorize a provider account. The recipient must complete authorization and select the publishing destinations. Generating the link alone does not connect the channel.

After authorization, check that the intended destination is connected in the intended workspace. Confirm publishing readiness before promising a launch date. Access to a provider account and selection of a publishing destination are separate steps. Use the connection guide for the relevant platform if a page is missing.

4. Establish the approval process

Open Workspace Settings and configure the approval workflow. Choose the required approval count and make sure enough active members can approve. The author cannot count toward their own approval.

For a restaurant launch, the agency writer can prepare the announcement, the account manager can check the destination and offer, and the client can review the final wording. Agree on a review deadline before the scheduled publishing time. If the time passes while review is pending, check the schedule before taking further action.

Campaign content review and workspace publishing approval are separate controls. An approved campaign draft does not bypass the workspace's publishing approval. Follow the campaign content and report guide when planning a group of posts.

5. Test one complete workflow

Start with one approved item. Confirm its workspace, content, media, destinations, and time zone, then review the delivery result. A scheduled item is not proof of successful publication. Check destination-level results before expanding to a bulk import or recurring workflow.

Google Sheets and Bulk Post support social publishing. For social posts, blogs, and supported Email workflows, API access and MCP can help connect your existing tools. Use a suitably scoped key and explicit workspace. An assistant still follows roles, approvals, plan access, and provider requirements. Email requires its separate add-on; not every dashboard tool has an MCP action.

6. Prepare a useful client report

Choose a consistent reporting period and review available metrics for the connected platforms. Use workspace or campaign report branding for client-facing reports. Explain what was published, what the available data shows, and the next action you recommend. For example, if a product demonstration receives more clicks than a teaser, propose a follow-up demonstration and explain the comparison period.

Missing provider data is not zero performance. Different platforms expose different metrics, and a publishing report does not establish a guaranteed sales result. Keep those limits clear when sharing results.

7. Review capacity and access as the relationship changes

Use Workspace settings > Usage limits to set optional caps for each client. For example, allow 20 publishing channels and 100 AI image requests per month while the client keeps an Admin role. Only the account Owner can change these caps. All limits are unset by default, and Apply to all workspaces can copy the policy across existing owned workspaces. Caps do not reserve extra account capacity. See Set Client Workspace Usage Limits for units, monthly resets, API/MCP access, and what happens at the limit.

Check shared account usage before adding another client. Publishing, CRM, Email, and AI media have distinct entitlements. CRM activation is separate from publishing activation; Email uses sending providers with their own charges and limits. Purchasing publishing channels does not automatically buy the other services.

When a teammate leaves or a client contract ends, review workspace membership, provider authorization, API keys, pending reviews, and scheduled work. Agree on the handover before disconnecting channels or changing access. Do not assume that another workspace has its own copy of the purchased allowance.

Continue planning

Reorganize a client’s connected channels

If a client’s publishing connections are in the wrong workspace, use Move channels to review a move into another workspace under the same owner. Posts and analytics stay in the source. Finish or cancel unfinished publishing work, resolve uncertain delivery, and remove any selected CRM allocations before moving. Recheck destination access and audience groups afterward.

The API/MCP flow previews the exact selection, then requires approval before confirmation with the same request ID and review token. Both workspaces require write access; MCP additionally requires workspace

and channels
consent. See the API reference and examples, and check the live action catalog for connector availability.

Previous guide

Recurring Posts

Set evergreen campaigns, repeated reminders, and recurring content schedules without rebuilding posts.

Next guide

Bulk Posting with CSV

Schedule social posts from CSV or Google Sheets, review each row, and set native AI disclosure labels on supported platforms.

Related guides