DigLab

Use ↓ ↑ to browse results, Enter to open, Esc to close.

Connect social accounts

Authorize the correct accounts, reconnect expired connections and avoid destination mistakes.

A social connection grants Social permission to work with a particular page, profile or channel. Connections belong to a workspace. Publishing, analytics and messaging may require different permissions on the same network.

Before connecting

Sign into the intended network account and confirm that you can manage the destination. Business pages may require administrator access. Confirm any network requirements for account type and linked pages in the connection dialog.

Connect and verify

  1. Open the intended workspace, then Settings → Social accounts / Social Connections.

  2. Choose Connect account and the platform. For Mastodon, provide the instance hosting the account.

  3. On the network's authorization screen, select the intended page or channel and approve the required permissions. Avoid selecting unrelated destinations.

  4. Return to Social. Confirm the exact account name, platform and connection status.

  5. Open New Post and check that the account appears as an available destination. Save a draft and inspect its preview before your first publication.

Reconnect an expired account

Open the failed connection and choose its reconnect or authorization action. Complete the network flow using the same intended account. Return to the affected post, check media and schedule, then retry only after confirming it has not already appeared on the network. If an account is missing, check the workspace first. Then check your role, network permissions, account type and whether authorization finished successfully. Do not disconnect a working account just to refresh a page.

Manage several brands

Keep each client's accounts in the correct workspace. Use Connect Links when available so a client can authorize their own accounts. Review every account selected by a destination preset; a preset is convenient but can become stale after a connection changes.

Check connection health before scheduling

A reconnect reminder means that the affected account needs attention before future publication can succeed. The composer may disable that account and explain that publishing permissions are required. Reauthorize the intended destination through its own provider flow, then verify it is selectable again. Reconnecting does not prove a failed post has been retried.

Check the account type and destination offered by the authorization dialog. For Facebook, distinguish a Page from a personal profile; for Instagram, check the eligible professional account and the connection route offered. LinkedIn profile and organization access can differ. Pinterest may require a board; YouTube requires a channel and audience/visibility choices. Do not infer another network’s permissions from a successful connection here.

Verify an existing connection

Open Settings → Social accounts or the Connect account link for the intended workspace. Check the exact platform and account, then confirm that it is available in New Post. Publishing, Inbox and analytics can have different permissions.

For a new connection, complete the network's own authorization flow and inspect the selected destination on return. A previously connected account is not a fresh OAuth test. A reconnect reminder applies to the affected account; it does not establish that all other accounts have failed.

Browse all DigLab docs →

DigLab Social · Practical product guides

DigLab