Connected accounts

Accounts are connected once for the whole workspace. Each event then either posts from your defaults, or from accounts you bind to it. That split is what lets one workspace run several clients’ events without a post going out from the wrong handle.

The account pool

Open Social Media → Connected accounts.

Every account you have connected appears here with its platform, its display name, and its status:

Each platform can have one account marked Default, used by every event that has not chosen its own. You can connect more than one account per platform — a second LinkedIn page for a different client, say — and only one of them is the default.

Connecting uses the BYO-OAuth wizard, where you supply your own app credentials and sign in with the account you want Novex to post from. Tokens stay scoped to your workspace.

Binding accounts to an event

Open the event → Social → Settings, and look for Post from.

• Tick nothing and the event uses your default account for each platform. The screen says so.
• Tick one or more accounts and the event posts from exactly those, and no others. The screen says that too.

Ticking is a replace, not an add: the set of boxes you submit becomes the event’s complete binding.

Rules enforced when you save:

• At most one account per platform. A second would never be used, so it is refused rather than silently ignored.
• The account must be connected. An expired or revoked account is refused at bind time, so the failure surfaces while you are looking at the screen instead of hours later against a live audience.

🔴 A bound event never falls back

This is the part worth knowing. If an event is bound and every bound account later expires or is revoked, that event has no account — it does not quietly fall back to your workspace defaults.

That is deliberate. Falling back would mean an event bound to Client A’s page publishing from your own default page the moment Client A’s token lapsed. “Bound and currently unreachable” is the honest state, and the settings screen shows it while somebody can act on it.

The practical consequence: reconnect the bound account. Setting a workspace default does not rescue a bound event.

How this is used elsewhere

• The composer resolves the event’s account when you approve a post, and refuses the approval if none resolves.
• The autopilot planner resolves the same way, so a composed post and a planned post always go out from the same handle.
• Metrics are read back through the connected account, so a disconnected account stops its numbers updating.

Permissions

Viewing needs social.read. Connecting, disconnecting and binding are managed through the connector screens — see Team & roles.

Related

• Autopilot — the rest of the event’s Settings tab.
• Meta App & assets — Facebook and Instagram share one Meta grant.