Available now
In build
The whole team
Nineteen specialists, each with a defined job and an honest status label.
See all nineteenThe business owner can safely delegate day-to-day posting to staff or an agency without giving away the ability to publish unsupervised.
Works with
What it does
Socie assigns each team member a role (owner, editor, approver, viewer) per connected account, controlling who can draft, who can schedule directly, and who must route through approval. Access can be scoped to specific platforms rather than the whole account.
A B2B software reseller brings on a junior marketing hire to help with LinkedIn posts, and within a week the owner realises this hire has exactly the same publishing access as the sales director — full ability to post to the company's LinkedIn page with nothing requiring a second look. Delegating day-to-day posting was the goal; delegating unsupervised publishing wasn't the intention.
Roles and permissions assign each team member a defined role — owner, editor, approver, viewer — per connected account, controlling who can draft, who can schedule directly, and who must route everything through approval first. Access can be scoped to specific platforms rather than the whole account, so a junior hire gets LinkedIn drafting rights without touching Facebook. The moment a role changes, that change needs to take effect immediately — a downgraded permission that still lets someone publish for a few stale minutes is a real risk.
Socie runs this directly on the platforms your customers already use — no separate app for them to install.
How it works
Each team member gets a role — owner, editor, approver, viewer — that can differ by connected platform, so a junior hire's LinkedIn access doesn't automatically extend to the company's Facebook or Instagram accounts as well.
An editor can draft and schedule within the bounds set for them, an approver reviews and signs off on others' drafts, and a viewer sees activity without being able to touch the publish queue at all in any way.
Whether a given role can schedule directly or must route through approval first is configured per account, so an owner decides exactly how much unsupervised publishing trust to extend to each role at each stage.
The moment a role is changed or revoked, that update takes effect at once rather than waiting for a session to refresh naturally on its own, so a downgraded account doesn't retain old publishing rights for even a few extra minutes.
Why it matters
The reseller's owner can hand day-to-day LinkedIn posting to a junior hire while keeping direct-publish rights restricted to a role that actually requires sign-off, rather than giving away full unsupervised access by default.
A hire brought on specifically for LinkedIn gets exactly that access, with no accidental reach into the company's other connected social accounts they were never meant to touch.
A role downgrade takes effect immediately, closing the gap where someone retains publishing rights they've just had revoked simply because a session hasn't refreshed yet.
The detail
The most operationally important detail here is timing, not the role definitions themselves. A permission change that only takes effect the next time a session refreshes — rather than the instant it's saved — creates a window where a just-downgraded editor could still publish, and for a business handling a compliance-sensitive product like a loan, even a few minutes of stale access is a genuine exposure. Role changes need to be enforced at every request, checked fresh each time, rather than cached in a way that lags behind current state.
For an agency managing several client accounts under one workspace, permission boundaries need to be airtight: one client's assigned team must never see or touch another client's content, drafts, or analytics, even by accident through a poorly scoped default. This isn't a tidiness concern — a client discovering a competitor's account manager could have seen their draft campaigns is a genuine trust failure, and access scoping exists to make that structurally impossible rather than depending on everyone remembering to be careful.
Role design also has a practical trade-off worth thinking through: giving every team member direct-publish rights removes the friction of approval, but also removes its safety net. A small business with one owner and one junior hire might reasonably want that hire's role to require approval on everything, since post volume is low enough that the extra step costs little, while an agency running high volume across many clients might need a more nuanced mix depending on how established each staff member is.
Industry use cases
7 industries where Socie applies this directly.
A B2B software reseller drafts three LinkedIn posts about a recent client rollout, routes them through an approval step to the sales director, and once approved they publish automatically on the days set in the calendar.
See the b2b sales playbookA regional NBFC's marketing associate drafts a post about a new loan product, and it sits in the approval queue until the compliance officer reviews the wording and either approves it or sends it back with a comment.
See the banking and finance playbookA coaching institute schedules a series of countdown posts leading up to an admission deadline, using AI-generated caption drafts that the academic head reviews before they go live.
See the education playbookA freelance graphic designer uses the AI content-idea generator to get five post concepts, turns two into drafts, and schedules them for the week so their profile stays active while they focus on client work.
See the freelancers and consultants playbookA physiotherapy clinic drafts a post about a new treatment offering, and the clinic owner reviews and approves the exact wording before it's allowed to schedule.
See the health and wellness playbookAn agency account manager creates draft posts for two different retail clients, sends each batch through that client's own approval workflow, and later exports a branded campaign report for each client separately.
See the marketing agencies playbookA real estate broker uploads photos of a new listing, generates a caption highlighting the property's key features, and schedules posts across Instagram and Facebook to go live over the coming days.
See the real estate playbookMore from Socie
The business can see everything planned across all social channels for the month at a glance, so gaps and clashes get caught before they become missed posting days.
Learn moreThe business writes a post once, customizes it per network, and it goes out automatically at the chosen time without anyone touching a phone.
Learn moreThe business gets a ready-to-post caption in seconds instead of staring at a blank composer box.
Learn moreThe business reaches more relevant people without manually researching which tags are trending in its niche.
Learn moreThe business never runs out of things to post, even during slow weeks with nothing obviously newsworthy to share.
Learn moreThe business gets a usable, on-brand social graphic without hiring a designer or opening editing software.
Learn moreQuestions
It has to apply immediately, at the exact moment the change is saved, rather than waiting for a stale session to refresh naturally on its own. A downgraded user retaining publish rights for even a few extra minutes is treated as a real risk, not a negligible technicality, particularly for a business handling anything compliance-sensitive like a financial product or loan offer.
Access is scoped specifically to prevent this — one client's assigned team should have no visibility into another client's content, drafts or analytics by default, however the workspace as a whole is structured. This boundary needs to be airtight rather than merely tidy, since a client discovering that another client's team could see their drafts is a genuine trust failure for the agency managing both accounts.
Yes — a role assignment can be scoped per connected platform rather than applying across a person's entire account access, so a hire brought on specifically for LinkedIn work gets exactly that reach without an accidental extension into the business's Facebook or Instagram accounts they were never meant to touch at all, from the very first day on the job.
It depends on the business's actual risk tolerance and posting volume — a small team publishing rarely might reasonably route everything through approval since the extra step costs very little, while a higher-volume agency might need a mix of direct-publish and approval-gated roles depending on how established each staff member is. There's no single correct default; it's a deliberate choice each business should make rather than leave at whatever's most convenient.
The rest of your stack
No rip-and-replace — control who can post and approve works alongside the systems already running your business.
Coming soon
