A practical SpreadPosts workflow

Get your workspace ready for its first post.

Start with access, one brand and one eligible destination. Verify a small publishing workflow before adding more accounts or activating advanced modules.

1. Join the workspace and secure your account

Create an account when public signup is available, or accept an invitation from a workspace owner. Verify your email and enable two-factor authentication in Account security before connecting a social account. Your role and brand access determine which screens and actions you can use.

2. Prepare the brand information

Create or open the brand you are authorised to manage. Add its source information, logo and review guidance. Check names, dates, prices and contact details against reliable sources; demo fixtures are not verified business facts.

3. Check destination setup before connecting

Open Features to see the module state, then Accounts to review connection options. A disabled destination needs setup or activation by the operator. Developers configure credentials securely on the server; never send client secrets, passwords or tokens through chat or a demo request.

4. Connect only accounts you can manage

Use the provider’s normal authorisation flow. LinkedIn profile publishing and company-page publishing have different permissions; a connected personal profile does not prove access to an organisation. Other providers may require developer approval, eligible account types or API funding. TikTok handoff is manual.

5. Review and schedule a small first post

Prepare a caption and supported media for one destination. Review the destination, timezone, date and exact revision, then obtain the required approval. If content changes after approval, use the normal re-review flow rather than assuming the old approval covers the edit.

6. Inspect the outcome and resolve blockers

After the scheduled time, check the post outcome and recorded receipt. Reconnect an expired account, resolve a visible validation error or ask the owner to check a paused workspace. An uncertain send needs investigation before another attempt. Demo results and a module marked available do not prove a live provider accepted a post.

What should I do when a module is Off?

Ask the workspace owner to review its setup requirements. Off can mean a disabled flag, missing provider credentials or a missing runtime dependency. Do not assume it is safe to enable the module without verifying its permissions and workflow. Planned means the feature has not been implemented.

Workflow guidance by TopGrade Software House. Actual module availability is shown in your workspace.

Keep exploring

Practical guides for your workflow.

A clearer approval workflow for social content.

When a writer, brand owner and client all contribute to a post, scattered messages can make it hard to tell which version was approved. A shared review workflow gives that decision a clear place.

Social content in English, Urdu and Roman Urdu.

Different audiences may need different wording, but the underlying facts should stay the same. Prepare language versions around one reviewed message rather than treating each caption as an unrelated post.

Your next content workflow

Bring your brand.
Build a clearer publishing routine.

Start with one post, the people who review it and the destinations that matter to your team.

Create your workspace