SOCIAL STUDIO

Sign in

1 Sign in → 2 Connect account → 3 Create test post

Advanced

OPTIONAL CAPABILITY

EILA Overwatch

Executive control is mounted—not coupled.

The dashboard already exposes the Social Studio contract. When the Overwatch runtime is connected, an executive assistant can build briefs, request approval, and run the same deployment lanes without changing Postiz or Tracer.

Adapter declaredRuntime connection optional

CONTROL PLANE

Advanced connection

Preview modeNo live API configured

Advanced API diagnostics. Routine access uses owner sign-in.

POSTIZ OAUTH

Connect a channel

BH

Black Hole CapitalNew channels join the default company workspace.

TikTok uses Social Studio's native Login Kit flow. Other networks use Postiz onboarding. Provider credentials and tokens remain server-side.

Select a provider to continue.

TRACER · LANCEDB

Campaign memory

Ask Tracer about brand voice, campaigns, audience signals, or prior deployments.

TEACH TRACER

Add scoped knowledge

Saved under the selected brand/tenant.

24/7 SUPPORT · AVAILABLE NOW

Social Studio Help Center

Run the whole social operation from one surface.

Search the guide or open a task below. These directions stay available in preview and live modes.

POPULAR HELP

Start with the job in front of you.

Quick startHow do I run my first deployment?＋
  1. Select the brand or tenant that owns the campaign.
  2. Select one connected channel or leave “All connected channels” selected.
  3. Choose feed, story, or reel; then write the caption and add an R2/CDN media URL when needed.
  4. Load Tracer context before approval so the deployment carries tenant-scoped brand and campaign memory.
  5. Choose draft, schedule, or publish now. Confirm the time for scheduled posts, then send the intent to the deployment lane.
  6. Verify the resulting state in Deployment Queue. Live publishing requires owner sign-in and a LIVE account.
ComposerDraft, schedule, and publish correctly＋

Draft stores the deployment without publishing. Schedule requires a valid local date/time. Publish now sends immediately through Postiz. Reels require a video URL. Use the campaign tag to group related queue entries and memory.

Preview mode simulates the queue locally. Live mode sends the payload through the Social Studio API and Postiz adapter.

ChannelsConnect and verify a social account＋
  1. Confirm the dashboard shows “Live control plane.” Sign in with your owner email and password.
  2. Select Connect account in Connected Accounts.
  3. Use Connect account in Connected Accounts. Postiz opens the provider OAuth flow.
  4. Finish provider authorization and return here.
  5. Refresh the dashboard and confirm the account shows LIVE before publishing.

Provider credentials and OAuth secrets belong in Postiz or the deployment platform—never in this browser build.

TracerSearch and teach campaign memory＋

Open Campaign Memory from the EILA Core4 panel. Search for prior voice, campaign, audience, performance, or content knowledge. Add new records with a clear label and one reusable fact or pattern per record.

Memory is always scoped to the selected brand and tenant. Loading context mounts the most relevant records onto the current deployment; it does not publish anything.

ModesWhat is the difference between Preview and Live?＋

Preview is a safe product demonstration with local sample channels, queue entries, and memory. Live requires the deployed API URL and owner sign-in and reads real Postiz/Tracer state.

The API endpoint may persist in the browser. Your session expires after eight hours and stays only in browser memory. Reloading requires sign-in.

DeploymentDeploy the dashboard and API＋
  1. Add CLOUDFLARE_API_TOKEN and CLOUDFLARE_ACCOUNT_ID to GitHub Actions secrets.
  2. Configure the Social Studio Worker with SOCIAL_ENGINE_ADMIN_TOKEN, POSTIZ_API_KEY, and TRACER_API_TOKEN. Add the two Tracer Cloudflare Access service-token values when Access protects Tracer.
  3. Deploy the isolated API Worker from capabilities/social-ops.
  4. Build the dashboard with SOCIAL_ENGINE_API_URL set to that public HTTPS Worker URL.
  5. Deploy dist/ to the isolated social-engine Pages project.
  6. Open /health, sign in as owner, refresh Channels and Queue, then run a draft before any live publish.

The complete copy-and-run procedure lives in docs/DEPLOYMENT.md.

SafetyWhat is Social Studio allowed to change?＋

Social Studio owns this dashboard, its API adapter, and its product deployment. Postiz and Tracer are replaceable mounted services. Do not alter AI Fans, EILA Overwatch, shared voice/video workers, another product’s Worker, tunnel, database, or persistent volumes to make this dashboard work.

TroubleshootingThe dashboard is not showing live data＋
  1. Check whether the top status says Preview mode.
  2. Open connection settings and check the HTTPS API endpoint under Advanced, then sign in.
  3. Confirm the Worker /health endpoint answers without leaking secrets.
  4. Confirm Postiz answers on its approved public URL and Tracer health is reachable through Access.
  5. Refresh Channels and Queue. Use a draft test before schedule or publish-now.
Live with EILAAssistant support mount is ready for the live adapter.