Frequently Asked Questions

We currently support Bluesky, Mastodon, Instagram, LinkedIn, and Threads. We may temporarily disable or update a provider flow when policy changes require adjustments.

Yes. You can connect multiple channel accounts where available. In queue and calendar views, use filtering to verify each draft before publishing.

No. We do not store provider passwords in plain text. We only store encrypted credential data needed for authorized publishing operations.

This can happen when metadata permissions are incomplete or stale, when token refresh is overdue, or when a provider blocks metadata temporarily. Reconnect the channel to refresh permissions and metadata.

Common causes are expired tokens, revoked channel access, unsupported media, or provider-side moderation restrictions. In many cases, reviewing permissions, token freshness, and media format resolves the issue quickly.

Workspace owners can disconnect and reconnect channels from channel settings. Removed channels no longer receive scheduled posts and are removed from active queue routing.

Multi-member workflows are in progress and part of the current foundation. Workspace members are supported, with stronger team collaboration controls planned before later phases.

Billing is out of scope for this cleanup phase. We are focusing on publishing reliability, queue behavior, and provider stability before paid plans.

Use the Contact form and include your workspace name, provider name, browser, and expected vs actual behavior. Screenshots and exact error text help a lot and usually speed up debugging.