On Dashboard → Social → Accounts, open the Add menu and pick a platform. Chirio hosts the OAuth flow and stores the tokens. Your organization ID is the Chirio profile — one connection set per workspace.
Before you connect
You need:
Social publishing enabled under Organization → Features
Access to the Social dashboard section (Audience manage capability)
Admin access to the Instagram or Threads account you want to link
Chirio configured on the Aveiro deployment (CHIRIO_API_KEY on the server)
If Chirio is not configured, the Accounts page shows an info banner and the Add button is disabled. Contact your workspace admin or Aveiro support — this is a deployment setting, not something you fix in the dashboard.
Supported platforms (Phase 1)
Platform
Add menu entry
Notes
Instagram
Instagram
Publishes to the linked Instagram account via Chirio
Threads
Threads
Separate OAuth from Instagram — connect both if you post to each
Each platform gets a row on the Accounts page listing its connected usernames, with an active or warning status tag.
Connect flow
Open Dashboard → Social → Accounts
Click Add in the page header and choose a platform
Your browser redirects to Chirio's hosted OAuth page
Sign in and grant the requested permissions
Chirio redirects back to — the account appears in that platform's row
Accounts
Connections are org-scoped. Every teammate with Social access sees the same linked accounts. Reconnect if a token expires or permissions change.
Using accounts in posts
When you expand a post:
Under Publish to, check the accounts that should receive this post
Each target gets the base caption unless you add a per-platform override
Attach media before approving — Meta fetches the public image URL at publish time
You cannot approve a post with zero targets. Connect at least one account first.
Agents use the same account IDs as targets when creating drafts via API or MCP. List them with GET /api/v1/social/accounts or the aveiro_social_list_accounts MCP tool.
Troubleshooting
Symptom
What to check
No connect buttons
Chirio may not be configured on this deployment — see the banner on the Social page
OAuth error after redirect
Retry the connect flow; confirm you have admin rights on the social account
Account shows warning status
Reconnect the account — token may have expired
Post fails at publish time
Open the row — per-target errors appear under Results; media URL must be publicly reachable
Social publishing available (on by default; re-enable under Organization → Features if you turned it off)
Access to the Social dashboard section (Audience manage capability)
Admin access to the Instagram, Threads, LinkedIn, or X account you want to link
Chirio configured on the Aveiro deployment (CHIRIO_API_KEY on the server)
If Chirio is not configured, the Accounts page shows an info banner and the Add button is disabled. Contact your workspace admin or Aveiro support — this is a deployment setting, not something you fix in the dashboard.
Supported platforms (Phase 1)
Platform
Add menu entry
Notes
No data availableThere are no items to display
Each platform gets a row on the Accounts page listing its connected usernames, with an active or warning status tag. X shows Paid plans on free plans — click it to upgrade.
Orbit (self-service connect)
Orbit targets hosted Supa Social instances. Pick Orbit from the same Add menu as Instagram and Threads — it opens a connect dialog instead of OAuth.
In your hub, open Connect and generate a one-time connect code
On Dashboard → Social → Accounts, open Add → Orbit
Enter the hub URL (for example https://orbit.dopler.app), the connect code, and the default space slug (for example general)
Click Connect Orbit — the account appears on Accounts like any other platform
Chirio redeems the code for credentials scoped to your organization. Codes are single-use and expire after redemption or timeout.
Hub posts support captions up to 2,500 characters. First comments are not supported — Chirio reports them as unsupported and never fails the post.
Connect flow
Open Dashboard → Social → Accounts
Click Add in the page header and choose a platform
Your browser redirects to Chirio's hosted OAuth page
Sign in and grant the requested permissions
Chirio redirects back to Accounts — a success toast confirms the connection (with @username when available), and the account appears in that platform's row
If OAuth fails, a danger banner on the page explains the reason plus any platform message from Chirio — common cases include cancelled authorization, an expired link, account limit reached, or a refused token exchange
Connections are org-scoped. Every teammate with Social access sees the same linked accounts. Reconnect if a token expires or permissions change.
Using accounts in posts
When you expand a post:
Under Publish to, check the accounts that should receive this post
Each target gets the base caption unless you add a per-platform override via Platform override
For Orbit targets, optionally pick a Space per account with the searchable space picker — type to search (debounced), use Load more for large hubs, or choose Default space to fall back to the slug from connect time
Attach media before approving — Meta fetches the public image URL at publish time
You cannot approve a post with zero targets. Connect at least one account first.
If you reconnect an account, it gets a new id — older drafts may still target the disconnected one. The editor shows a Disconnected accounts warning with a one-click remove; Approve and Post now refuse until targets are fixed.
Agents use the same account IDs as targets when creating drafts via API or MCP. List them with GET /api/v1/social/accounts or the aveiro_social_list_accounts MCP tool.
