# Social Connections

Social Connections links your org's X, Instagram, and Facebook accounts to TheContentForge via OAuth. Once connected, you can publish and schedule posts directly from generation surfaces, and tracked profiles can feed analytics back into the Dashboard and Patterns.

### Who can use it

Org owners and Admins connect, disconnect, and manage profile settings. Once a profile is connected and marked postable, any user can publish through it from the generation surfaces unless the org's Approval Workflow is enabled. When approval is enabled, send behavior is gated by the configured minimum approver role.

### What you can do

* **Connect via OAuth** - X, Instagram business accounts, and Facebook Pages
* **Per-profile toggles** - mark each linked profile as trackable for analytics and/or postable in the Publish Panel
* **Default profiles** - choose which profile should be preselected for each platform
* **Analytics sync** - fetch metrics for tracked profiles manually, with hourly sync keeping data fresh
* **Connection status** - see display name, external user ID, scopes, token expiry, and last-refreshed timestamp
* **Sync log** - audit trail of ingest runs: posts ingested, conflicts resolved, timestamp, and errors

### How to connect

1. Sign in as an org owner or Admin and open **Social Connections**
2. Click **Connect Meta** for Facebook/Instagram or **Connect X** for X
3. Complete the OAuth flow on the provider's site
4. Return to Social Connections and review the discovered profile(s)
5. Toggle **Track** and **Publish** for each profile you want active
6. Set the default profile for each platform if more than one is available

Connections are org-scoped. One connection can expose multiple profiles, and those profiles are managed independently.

### Track vs Publish

**Track** means analytics from that profile can be ingested into Dashboard and Patterns.

**Publish** means the profile is available in Publish Panels for Content Forge and Video Forge.

Turning both toggles off parks the profile. Parked profiles remain connected, but they do not count against the active social profile limit.

### Disconnecting

The disconnect button does a hard disconnect:

1. Revokes the access and refresh tokens on the platform side when supported
2. Removes the connection and profile rows, including encrypted credentials
3. Clears OAuth state for that provider so the next connect starts clean
4. Cancels scheduled posts using those profiles while preserving historical analytics rows

If you want to fully revoke the OAuth grant on the platform itself as well, visit the platform's connected-apps settings.

### Plan limit

Plans limit **active social profiles**, not raw OAuth connections. A profile counts when either **Track** or **Publish** is enabled. A usage bar on the Social Connections page shows where you're at, and parked profiles do not count.

### Related

* [Publishing](/thecontentforge-docs/feature-guides/publishing.md) - Publish or schedule posts through a connected account
* [Calendar](/thecontentforge-docs/feature-guides/calendar.md) - See scheduled, manual, and published posts in one place
* [Dashboard](/thecontentforge-docs/feature-guides/dashboard.md) - Review analytics from tracked profiles


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://thecontentforge.gitbook.io/thecontentforge-docs/feature-guides/social-connections.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.