# Authorise a social connection and choose the right accounts

> Complete provider consent in the same workspace and explicitly select the destinations you intend to connect.

Canonical HTML: https://proplix.co.uk/help-centre/social-automation-oauth-account-selection/

Topic: Social Media Automation

Reviewed: 13 November 2026

## Where to start

Social accounts → Connect → provider consent → account selection

## Before you begin

Sign in to the intended test or organisation-owned account at the provider. Check the account and workspace before approving access.

## Fields and options

- **Access needed:** Manage connections and authorised control of the provider account
- **Selection:** Multiple discovered destinations require an explicit choice; selecting none is not a request to connect every account.
- **Callback state:** The connection flow binds the callback to its initiating workspace and staff identity and consumes it once.
- **Cancellation:** Declining provider consent does not create an invented connected account.

## Follow these steps

1. Choose the provider’s Connect action from Social accounts. Review the official provider page and the permissions requested.
2. Approve only when the app, account and permissions match your intended use, then let the provider return to the workspace callback.
3. When multiple destinations are discovered, explicitly select the authorised accounts or boards you want to save and submit the choice.
4. Return to Social accounts and check the provider, display name and destination identity for every saved connection.
5. Use Verify connection before composing a controlled first post.

## Check the result

Check the selected destination identities and run Verify connection. Confirm unselected accounts were not silently added.

## Troubleshooting

For an expired or already-used flow, start Connect again from the correct workspace. For an empty destination list, check account eligibility, app products, provider permissions and administrative rights at the network.

## Fields, rules and limits

- Do not reuse an old callback address or share its code/state with another person.
- A provider grant can be rejected when its explicitly returned permissions omit required scopes.
- Discovery and connection saving are not publishing; keep the direct-publishing gate locked until a deliberate test is ready.

## Questions and answers

### Can I finish someone else’s callback?

No. The flow is tied to the initiating staff identity and workspace.

### Why did it ask me to choose an account?

The provider returned more than one destination, so the module requires an explicit selection.


## Related guidance

- [Social Media Automation: account setup to verified publication](https://proplix.co.uk/help-centre/social-automation-complete-feature-guide/index.md)
- [Verify, renew and disconnect social accounts](https://proplix.co.uk/help-centre/social-automation-verify-renew-disconnect/index.md)

Product reference: https://britixo.com/help-centre/social-automation-oauth-account-selection/
