Publish from Studio

Connect channels

1. Step 101

   Open Channels

   Publish → Channels lists the networks this deployment supports, each with its character limit, image count and status. Your plan's channel quota shows at the top.
2. Step 202

   Connect

   Most networks sign you in with OAuth. Mastodon asks for your instance URL first; Bluesky takes an app password. When one sign-in manages several accounts (a Facebook business, a LinkedIn organization), a second step asks which accounts become channels.
3. Step 303

   Set defaults

   The wizard's last step sets what new posts to that channel start from. Change it any time from Channels.

A channel is Connected, Reconnect needed (the network's access expired; scheduled posts on it are blocked until you reconnect, and the owner is notified) or Disconnected. Connecting needs the organization policy that allows connectors; grouping channels by client, pausing a channel and the invite link need an organization admin.

Compose and preview

New post opens the composer: pick channels, write the shared text, then tune each channel on its own tab. The counter shows the limit of the channel you are on and how far over you are; a reply in a thread over the limit is flagged too. Threads (several parts) work on X, Bluesky, Mastodon and Threads; a first comment works on LinkedIn, Facebook and Instagram. The AI assist can improve or shorten the text, write alt text for an image, and suggest hashtags, which are appended to the text.

From a Studio piece, Schedule posts prefills the composer with its captions and cards, rendered at each channel's exact size when the post goes out; Post the cover as an image renders the cover and opens the composer with it attached. The preview pane shows the post as each channel will display it.

Media

Attach images or video from your Library, upload a file, or (with v3) pick a Studio page, which is rendered to PNG with drafted alt text. Library and uploaded items need alt text before you can schedule. The table above gives each platform's maximum count and size; the composer validates them per channel before it lets you schedule.

Schedule, review and the queue

Pick a time and an IANA time zone (the post's own, then the channel default, then the workspace default, then your browser's), or publish now. The Publish calendar shows week, month and list views; the queue rail counts what is scheduled, needs approval, failed, and was sent in the last seven days, and warns when channels need a reconnect. Edit a post to move it to another time.

Team review

Send a post for review and a teammate who is not its author approves it or requests changes with a comment; an approved post is scheduled at once. An organization can require review for every post with the social approval policy, which the composer then says plainly.

Results

Impressions, engagements and clicks are collected nightly for posts of the last 30 days and shown on the queue rail, per post, and (with v3) as statistics over 7, 30 or 90 days with likes, comments and shares, a comparison against the previous period, a best-time suggestion, and a client filter. Posting slots can be filled from the best times the data suggests.

v3: sets, signatures, clients and short links

STUDIO_PUBLISH_V3 is a deployment flag, off by default. Where an operator turns it on, Publish adds:

• Sets — a saved group of channels with per-channel settings, picked in one tap from the composer; signatures — reusable text appended to a post, with an auto-add option. Both are managed from the Channels page; everyone can use them, admins create and edit them.
• Posting slots and the day view — fixed times per channel that shape the day view and Next free slot; tags to color the calendar; repeats for a series.
• Clients — group channels by client to filter the calendar, the channel list and the composer; invite links that let a client sign in to their own network and land their channel under that client (single use, seven days, OAuth networks only, up to 50 open at a time).
• Client preview links — a seven-day link that shows a post per channel and takes guest comments; pause a channel; duplicate a post; Draft with Akili, which writes a draft per channel from a brief, in short or long form, as a post or a thread, without publishing anything.
• Automations — install a ready-made flow for a channel (auto-repost once a post passes a like count, auto-plug) and edit it in Flows; webhooks scoped per channel for post published and post failed events.

Short links are a second flag, STUDIO_SHORT_LINKS, also off by default. On, links in a post are rewritten to /l/… on your Akili host when it publishes and clicks are counted (bots and HEAD requests are not). The organization policy decides whether to ask on each post, always shorten, or never; the composer shows a Shorten links toggle in the ask mode and tells you which links a network keeps as they are.

API scopes

A platform API key with no scopes keeps its owner's access; a scoped key gets only what it names, and social:write implies read. Sets, signatures, invites and client groups use the same scopes under v3.

Good to know

• Credits. One credit per published item by default, only for items that went out. A deployment can change the price.
• Networks that need app review. Facebook, Instagram, Threads, TikTok, YouTube and Pinterest require the network's own app review of the deployment; until the platform administrator has set one up, the Channels page shows it as not set up yet.
• Comments on a post. Teammates can discuss a post in its comment thread with @mentions, separate from a client's guest comments on a preview link.
• Flows and Publish. Flows can repost or comment on a published release and draft posts per channel; see Triggers and nodes.
• Mobile. The Akili app has Channels, Compose and the queue, so you can approve and reschedule from your phone.
• Switched off. An operator can turn the whole Publish surface off; the page then says social publishing is off on this deployment.