The use case
A concrete agency workflow is on the agencies use case.
By company
Connect that client's profiles and ad accounts, then run Lab, Post, and Campaigns without mixing brands.
The retainer
One per client. Their profiles and ad accounts stay with that contract.
Lab writes the draft. Post holds the week. Campaigns holds the flight. The team edits the same work.
The calendar and the flight are what you walk through. The draft stays next to the post it was written for.
How it works
Create one for the client on Team workspaces.
Link profiles and ad accounts in Connections.
Invite the client in Collaborate. Keep publish with agency roles, and admin with leads.
Queue Post, draft in Lab, and open Campaigns for the flight.
Why agencies use it
A concrete agency workflow is on the agencies use case.
Buyer-heavy pods can start from performance marketers.
Questions
Create a workspace per client and connect that client's profiles and ad accounts. Lab, Post, and Campaigns for that brand stay inside the workspace.
Invite the client as a member. Keep publish with the agency roles you choose, and leave admin actions with leads.
The calendar in Post and the flight in Campaigns. A Lab draft stays in the workspace, next to the post or campaign it was written for.
Agencies
Connect their accounts, invite the approver, and keep the week and the flight in that workspace.