← All experiences
SocialPatio

Social channels, with the right permissions.

Connect account authority, publishing and conversation to the work behind them. SocialPatio is a proposed infrastructure layer for products that operate across social channels.

The Patio atlas

Inside SocialPatio.

Choose a topic or browse every data resource, capability and integration. Open an item to see what connects to it.

57items

Explore by topic

SocialPatio

Browse all items 57

1–18 of 57 items
Page 1 of 4

The catalog distinguishes upstream building blocks from proposed Patio connections. These are not live account bindings.

Inspect item

The workflow lab

See the records change.

Choose an incoming case and a recipient permission. Inspect the field mapping, the records kept and the exact handoff.

Fictional sample data

SocialPatio / Workflow

Keep a reply bound to what was approved

Follow a comment into an exact reply intent. Edit the content or remove the qualified capability and see the action stop.

Recipient permissionFollow-up context in MailPatio
Current resultReply intent bound to the approved revision
1local records2source relationships
SocialPatio. Exact approval + qualified capability. Reply intent bound to the approved revision. Selected projection available. 4 Fields received.
01

Source records

What arrived, with its context

LinkedIn comment context
social.comment
postRef
urn:li:share:sample-42
commentRef
comment:73
actorRef
member:sample-a
All fields & provenance5
text
Can you share the onboarding guide?
observedAt
2026-10-28T10:00:00Z

Fictional official-API record. Public comment identity stays separate from a CRM or email identity.

Reply approval
social.reply-review
draftRevision
3
approvedRevision
3
destination
comment:73
All fields & provenance6
approvedAccount
organization:studio-demo
partnerCapabilityQualified
true
text
Here is the reviewed onboarding guide.

The example assumes an explicitly qualified capability only in the qualified branch.

02

Mapping & decisions

What changes, what stays separate

01Retained
provider.commentRefcomment:73
conversation.externalRefcomment:73
Mapping rule

Retain the native identity rather than create a new social person.

02Mapped
draft.revision3
approval.matchestrue
Mapping rule

Content edits invalidate approval of the earlier revision.

03Mapped
qualified partner capabilitytrue
reply.eligibletrue
Mapping rule

Provider product, scopes and roles must support the exact effect.

Reply intent bound to the approved revision
Why this decision?

The exact account, comment and content revision are eligible for a separately executed reply. Nothing has been published by this lab.

Link the request, not the person’s accounts
Why this decision?

A follow-up reference can connect this request to a workspace task without guessing the author’s email address.

03

Resulting records

What this product keeps

Exact reply intent
social.reply-intent
destinationRef
comment:73
contentRevision
3
approvedRevision
3
All fields & provenance5
eligibility
ready
publicationState
not_sent

Native publication and its receipt would remain separate execution steps.

Typed handoff

SocialPatioMailPatio

social.followup-context.v1
Selected projection available
Fields received
requestRef
comment:73
topic
onboarding guide
approvedContentRevision
3
workspaceTask
task:guide-followup
Remain outside this handoff
actorProfileprivateInboxguessedEmailunrelatedComments

Only these selected fields cross into the receiving product.

Sample grantdemo-grant:socialpatio:mailpatio:social.followup-context.v1
Inspect the rules and source foundations3

One official account, comment and reviewed content revision. No publication or inferred identity merge occurs.

ContractSpec supplies the cited building blocks. This end-to-end recipe is a proposed Patio composition; its fixture decisions do not run those services.

A local simulation. No account is connected and no message, publication or deployment is sent.