How to Run One Item 12 Workspace Per Client (Agency Playbook)
· how-to
Marketing agencies that grow LinkedIn for clients hit the same wall: every account lives in a different login, spreadsheet, and automation tool. Context disappears when you switch tabs — and one wrong send can damage a client relationship overnight. The fix is structural: one Item 12 login, one isolated workspace per client, with its own LinkedIn connection, CRM graph, credit balance, and MCP scope. This playbook walks through setup, daily ops, and the guardrails that keep client data from mixing. For the full agency story, see /for/marketing-agencies.
Why one workspace per client (not one mega-org)
Item 12 workspaces (organizations) are fully isolated — contacts, inbox threads, pipeline stages, agents, scheduled posts, and credits never bleed across org boundaries. That matches how agencies think: Client A is not Client B. A single mega-org with tags works for internal SDR teams; agencies need hard separation so a VA searching in the wrong list cannot enroll Client B prospects into Client A's sequence. Related: /blog/agency-outgrown-shared-linkedin-logins.
Step 1: Create a workspace per client
From the workspace switcher, create a new organization named after the client (e.g. Acme Corp — LinkedIn). Use a consistent naming convention: ClientName — LinkedIn or ClientName — Outbound. Your agency operators keep one Item 12 account and switch workspaces from the sidebar — no separate email per client.
- One workspace = one client's LinkedIn account + one CRM graph
- Credits and Teams billing are per workspace — pass through to client retainers or centralize on agency card
- Duplicate workspace names are fine; use internal notes in your agency runbook for workspace IDs
Step 2: Connect the client's LinkedIn in Settings
Inside the client workspace, go to Settings and connect LinkedIn via hosted OAuth. The client (or their delegated exec) authorizes once — reps never need the LinkedIn password. Each workspace holds exactly one primary LinkedIn connection for that client account. If you run outbound from the CEO's profile, connect the CEO's LinkedIn in that client's workspace only.
Step 3: Invite your pod with workspace-scoped roles
Invite strategists, VAs, and optionally the client as owner, admin, or member on that workspace only. They see mirrored inbox, pipeline, lists, and the review queue for that client — without access to other clients' workspaces. Revoke a contractor by removing their seat; no password rotation on the client's LinkedIn. Deep dive: /blog/agency-linkedin-team-seats-no-password-sharing.
Step 4: Issue MCP tokens per client (optional)
MCP tokens bind to a workspace. Create one token per client (or per pod) in Settings → API bridge so Claude, ChatGPT, or Cursor tools only read and write that client's CRM graph. Before any MCP batch import, confirm the active workspace in the Item 12 UI — never cross-contaminate contact lists. Setup guide: /blog/agency-mcp-linkedin-crm-setup.
Step 5: Standardize lists, tags, and pipeline per client
Clone your agency SOP into each workspace: default pipeline stages (Lead → Contacted → Meeting → Won), tag taxonomy (outbound-cold, webinar-lead, content-engager), and one or two starter lists. Profile URL is the canonical contact key — imports dedupe automatically. When onboarding a new client, copy structure from a template workspace rather than rebuilding from scratch. See /blog/linkedin-agency-client-onboarding-mistakes.
Step 6: Daily switching workflow
- Morning: open workspace switcher — triage Client A inbox and review queue first
- Before prospecting: switch workspace, verify org name in header, then run LinkedIn search or MCP import
- Before any send: confirm pending items in review queue belong to the active workspace
- End of day: MCP or dashboard snapshot per client for tomorrow's standup
Step 7: Client visibility without credential sharing
Invite clients as members on their workspace so they see inbox, pipeline, and what queued for approval — you control seats and permissions. Weekly calls pull from live pipeline and mirrored threads instead of screenshot decks. Reporting workflow: /blog/agency-weekly-linkedin-pipeline-review.
Can one agency login manage 10+ client workspaces?
Yes. One Item 12 user can belong to many organizations. Switch from the sidebar; data never mixes between orgs.
Does each client need their own Teams plan?
Credits and Teams billing are per workspace. Many agencies put each client on their own workspace with separate credit pools; contact sales for multi-workspace volume.
Will agents auto-send on client accounts?
No. Every LinkedIn message and invitation queues for human approval — critical for agency brand safety. See /blog/agency-linkedin-human-review-queue.