Channel already connected to another workspace
If you try to connect a social account and see an error like "This channel is already connected to another workspace", it means the same underlying account is in use by a different Schedulin organization.
Each social account can only belong to one Schedulin workspace at a time. This prevents two teams from accidentally double-posting to the same audience.
Common scenarios
- You created a personal workspace first, then joined a team workspace — the channel is still attached to your personal one.
- An ex-team-member connected it under their workspace — even after they leave, the channel stays attached until removed.
- An agency connected it before handing it off — the agency still owns it on their side.
How to fix it
You need to disconnect the channel from the other workspace before connecting it here.
If you have access to the other workspace:
- Switch to that workspace from the workspace switcher.
- Open Channels, find the account, and disconnect it.
- Switch back and retry the connection.
If you don't have access:
- Ask the workspace owner to disconnect it on their side.
- Or, as a last resort, revoke Schedulin's access from the social network's own settings (e.g. Meta Business Settings → Connected Apps, X → Settings → Connected Accounts). The next API call will fail and we'll release the channel within a few minutes — at which point you can connect it to your workspace.
Agency hand-offs
If you're an agency handing a client off, the cleanest sequence is:
- Disconnect the channel from your workspace.
- Have the client connect it in theirs.
- Re-add yourself as a member of the client's workspace if you'll still be managing it.
Don't try to "transfer" by changing the OAuth token — disconnect and reconnect is the only supported path, and it preserves analytics on each side.
Still stuck?
If you've disconnected from the other side but the error persists, contact support. We can verify the channel's state on our end and force a release if a cleanup didn't propagate.