CONNECTIONS

# Platform Connection Setup

The Core setup wizard now includes an actual connection step for every network selected in the first wizard step.

A selected network must be either:
- successfully **Connected & Tested**, or
- explicitly **Skipped for now**.

DivisionDesk does not mark a network connected merely because credentials were entered.

## Credential handling

For the official DivisionDesk Social Media package on Core, non-secret account identifiers are stored in package-scoped storage. Access tokens, app passwords, refresh tokens and similar secrets are stored in Core's encrypted SecretVault. They are not rendered back into forms.

## Current connection method

Developer Platform 1.0 does not freeze a generic client-module OAuth-broker endpoint on DivisionDesk Server. This package therefore does **not invent one**. The wizard accepts provider-issued credentials/tokens and validates them against the provider before marking the connection successful.

A future centralized DivisionDesk OAuth broker should be added only after the Server API contract is formally frozen.

## Provider notes

- Facebook Pages: Page ID + Page access token.
- Instagram Professional: Instagram user ID + authorized access token.
- X: OAuth 2.0 user access token with appropriate scopes.
- LinkedIn Pages: organization URN + authorized access token.
- YouTube: OAuth access token; refresh token is recommended for long-running automation.
- Bluesky: handle + App Password + PDS URL.
- Mastodon: instance URL + user access token.
- Pinterest: board ID + authorized access token.
- TikTok: approved Content Posting/Login integration + user access token.