How do agency credential pools work in PostMimic?

Connect platform logins once into a pool, then assign them to client profiles so each voice publishes on the right accounts. Credential pools exist for agency-style ops: fewer reconnects, clearer mapping between who is speaking and where it publishes.

Soft note: credential pools are an Agency-tier style capability for multi-client work—useful when you outgrow one-login-per-chaos. Exact plan packaging lives on the pricing page; the workflow below is the operational idea.

The reconnect tax agencies actually pay

Multi-client social fails in boring ways:

• Someone reconnects LinkedIn for Client A and accidentally leaves Client B’s draft pointing at the wrong destination
• A contractor leaves and takes “the login in their head” with them
• The same Facebook Page gets re-authorized three times in a quarter because nobody owned the connection
• Profiles sound right, but publish targets drift because credentials lived in screenshots and Slack

That is the reconnect tax: time, risk, and trust burned on access plumbing instead of voice and creative. Pools attack the plumbing problem so profiles can stay about writing voice and brand rules.

Pool vs per-profile credentials

Per-profile credentials mean each client profile carries its own connected accounts. That is fine for a single brand or a tiny roster. It gets messy when the same agency operator jumps between ten clients and re-auths the same networks repeatedly.

A credential pool flips the model:

1. Connect platform logins/accounts into a shared pool once (Pages, company channels, and other supported destinations you control).
2. Assign pool entries to the client profiles that should publish there.
3. Keep voice training and brand rules on the profile—credentials are assignment, not personality.

Think: pool = keys on the agency ring; profile = the client’s mouth and manners. Mixing those concepts is how Client A’s tone ships on Client B’s Page.

Facebook reminder for every client: Pages only, not personal timeline.

Assign to the right voice

Assignment discipline matters more than the feature name.

Good practice:

• One client → one primary profile (or a small, intentional set if they truly have distinct spokespeople)
• Map each profile only to the accounts that spokesperson or brand is allowed to use
• Never “temporarily” point a draft profile at another client’s Page to test formatting
• Review the mapping when staff changes, when a Page admin changes, or after any reconnect

Voice cloning from real posts only helps if publish targets match the identity you trained. A perfect Client A draft on Client B’s Page is still an incident.

Phone, web, and desktop should all see the same profile→account truth so a late approve on mobile cannot invent a new mapping.

Keep rules on the profile (not only in Slack)

Credential pools do not replace brand safety. Each client profile still needs:

• Allowed / forbidden topics
• Tone and forbidden phrases
• Alliances and opponents
• Claims and disclaimer policy

Rules travel with the voice. When a pooled credential is assigned to that profile, drafts still pass the client’s checklist before schedule or publish. Optional Agent Mode—if you use it at all—belongs only after a clean manual-approve streak for that client, not because the agency “already trusts the tool” globally.

Agency-style ops fail when rules live in a shared Notion page nobody opens while credentials are carefully pooled. Pool the logins; profile the boundaries.

Ops checklist for a clean pool

Use this when you onboard or audit:

1. Inventory client Pages and channels you are allowed to operate.
2. Connect them into the pool with a named owner (not a personal contractor login when you can avoid it).
3. Create/confirm the client profile and import that client’s real posting history.
4. Write brand rules on the profile.
5. Assign only the correct pool credentials to that profile.
6. Send a test draft through manual approve to the right destination.
7. Document who can reassign credentials and who can turn automation on/off.
8. Re-audit after staff changes or platform re-auth prompts.

If step 6 fails (wrong account, wrong tone), stop. Fix mapping or rules before volume.

Failure modes to watch

Pools reduce reconnect chaos; they do not remove judgment. Watch for:

• Wrong assignment — a pool credential attached to the incorrect client profile after a rushed onboard
• Stale auth — platforms expire tokens; a pooled connection still needs an owner who responds to re-auth prompts
• Over-sharing access — too many people can reassign credentials, which recreates the contractor-laptop problem in software form
• Voice/profile drift — training data updated on the wrong profile while publish targets stay correct (or the reverse)
• Automation too early — Agent Mode enabled for a client because “the agency is used to the tool,” not because that client’s manual streak was clean

Run a monthly ten-minute audit: profile list, assigned accounts, last successful publish, named owners. Boring audits beat exciting incident channels.

Try Free on one client first

Even if pools are an Agency-tier ops feature, prove the voice loop on one client first via Free at https://postmimic.app: import their archive, set rules, approve drafts by hand, and confirm the publish target. Scale pooling after one client’s path is boringly correct—not before.