Managing and disconnecting connections

Status chips tell the truth

Every row carries a status chip, and Pinnora computes it on the server from the real token and vendor state, not from a guess. The states you will see are connected, expiring, attention, and not available. Broken or expiring connections float to the top of their category, so the thing that needs you is the first thing you see. If the page cannot read status for some reason, it shows a plain error card rather than quietly drawing everything as "Connect", so you are never tricked into thinking a dead connection is fine.

Watch the expiry

Some connections, Meta in particular, use tokens that cannot refresh themselves. A Meta token is like a parking meter: it will not top itself up, and when it runs out, whatever was feeding on it stops. When one of these is within about a week of expiring, the row shows a countdown. Reconnect before it lapses so your scheduled posts and pushes keep running.

Reconnecting

When a token expires or gets revoked at the provider, the row switches to a reconnect state and any pushes that depend on it are parked until you act. Reconnecting runs the same approval flow as the first connect and restores the setup you already had, so you are not rebuilding from scratch.

Disconnecting

Every connection has a disconnect control sitting next to its connect control. Disconnecting removes the stored token or vendor link. Anything that was relying on it, a social channel in your calendar or an ad account in the Ads Manager, stops working until you connect it again. Disconnect when you are rotating credentials or retiring a service, not to clear a passing error. A healthy connection does not need it.