AAtlasLoopOSGTM operating system
Betaatlassocial

Move from permissioned content sources to approved social publishing.

Plan and approve social content through permissioned workspace data, then publish approved X/Twitter posts immediately or through the durable scheduled queue when an account is authorized. Facebook, Instagram, and LinkedIn remain draft/schedule-only placeholders.

Open authenticated workspace Read step-by-step guideProduct catalog

Runtime availability depends on the canonical product status, organization entitlement, workspace permissions, deployment configuration, and any provider-specific authorization required by the workflow.

Who it is for

  • Content and growth teams that need idea generation, platform-specific drafts, explicit approval, scheduling, and controlled X/Twitter publishing inside a workspace.

Codebase contract

  • Application route: /products/atlassocial
  • Required permissions: atlassocial.access

How the current workflow works

  1. 1Select an entitled organization and workspace.
  2. 2Review the imported content sources that AtlasSocial can use for idea generation.
  3. 3If X/Twitter publishing is required, connect the workspace account through the configured OAuth flow.
  4. 4Generate post ideas from selected source IDs or the available source set.
  5. 5Generate platform captions from an idea or source and choose the intended tone.
  6. 6Review each draft and explicitly approve or reject it.
  7. 7For an approved X/Twitter draft, publish now or schedule it for the durable provider-backed queue.
  8. 8Review the scheduling calendar and draft status; treat Facebook, Instagram, and LinkedIn as draft/schedule placeholders until separate publishing integrations exist.

Current codebase capabilities

  • Workspace-scoped source, idea, draft, and calendar views.
  • Idea generation and platform-caption generation from permissioned source records.
  • Explicit approve and reject actions before publishing.
  • OAuth-based X/Twitter connection with encrypted workspace tokens.
  • Immediate and scheduled X/Twitter publishing for approved drafts.

Current boundaries

  • X/Twitter is the only real publishing provider in the current Beta.
  • Facebook, Instagram, and LinkedIn remain draft/schedule-only placeholders.
  • Publishing still requires an approved draft and a configured provider connection.
  • The product does not grant unsupervised publishing permission.

Manifest capabilities and permissions

These identifiers are read directly from the canonical frontend product manifest. They describe access boundaries and capability names; they do not by themselves prove provider configuration or runtime availability.

Capabilities

atlassocial.accessatlassocial.posts.publishatlassocial.publish.twitteratlassocial.api.validate_license

Required permissions

atlassocial.access

What to verify after using it

  • The selected workspace shows the intended content sources and generated drafts.
  • The X/Twitter connection reports connected before a real publish action is attempted.
  • Approved drafts show the expected approval and publish/schedule status in the workspace.