Help & support

In the admin dashboard, go to Clients and choose New client. You need a name and a timezone. The timezone matters: everything the client sees, and every schedule you set for their accounts, is displayed in it. You can also decide here whether their content needs their approval before it can be scheduled.

Open the client and use Invite client. They receive an email invitation, set their own password, and land in their own dashboard. They will only ever see their own data — client accounts cannot be given access to more than one client.

The admin dashboard is the full operational surface: clients, accounts, content, calendar, scheduling, automation, logs and settings. The client dashboard is deliberately much smaller — reviewing content, seeing what is scheduled and published, checking account status, and contacting you.

You start the connection from the client’s Accounts tab and the account holder completes it on the platform’s own authorisation screen. They sign in with the platform directly and choose which permissions to grant. No password is shared with you or with us, and two-factor authentication stays on.

Yes. A client can have as many accounts as they need, including several on the same platform. Each is connected, scheduled, monitored and reported on independently.

Connected means the authorisation is valid and publishing works. Authorisation expired means the token could not be refreshed and the account holder must re-authorise. Permission issue means the granted scopes do not cover what was attempted. Rate limited means the platform is throttling us and publishing will resume on its own. API error and Needs attention mean something requires a manual look.

An approved developer application for each platform you want to use, with its credentials set in the deployment environment. Until those are configured, the platform appears in the product as not configured rather than offering a connect button that cannot work.

Upload the video once as a content item, then add a destination for each account. Every destination gets its own caption, hashtags and publish time, and tracks its own status. The file itself is stored once, not duplicated per destination.

Draft, then Pending review, then Approved, Scheduled, Publishing and Published. A client can also reject, which stops the post, or request changes, which sends it back to draft with their comment attached.

Yes, per client. If a client does not require approval, content moves straight from draft to scheduled and publishes without a review step.

No. Scheduling runs entirely on the server. Once a post is scheduled and approved, it publishes whether or not anyone is logged in.

Every time is stored in UTC internally and displayed in the relevant account or client timezone. When you pick a time you are picking a wall-clock time in that account’s timezone, so daylight saving changes do not shift your schedule.

The system is built specifically to prevent it. Only one live job can exist per post, workers hold an exclusive lease while publishing, each job carries an idempotency key, and the platform’s post identifier is recorded under a unique constraint so a retry after a lost response cannot create a duplicate.

Open Failed Posts. Each failure shows the exact reason reported by the platform. Temporary problems — rate limits, network errors, platform outages — are retried automatically on a backoff. Permanent problems are not retried, because retrying them would only fail again; fix the underlying cause and then retry manually.

We only show figures a platform actually returns through its API for that account. If a platform does not report a metric, or has not reported it yet, the product says so rather than showing a zero that would read as real.

No. Clients see only their own accounts and their own numbers. Only agency administrators see across clients.