FlowOS Automation HubPlain-English product documentation

Before you start

  • Platform administrator access with MFA.
  • Payment providers kept in sandbox until approval.
  • Database and backup ownership documented.

#Provision and verify a workspace

  1. Create the workspace identity and database connection.
  2. Test connectivity without exposing credentials.
  3. Run tenant migrations and seed required permissions.
  4. Assign the approved plan.
  5. Verify tenant login and readiness.
  6. Record backup and support ownership.

#Use plans and billing as enforced controls

Plans define limits and feature availability. Tenant billing shows current plan, usage, checkout, renewal state, coupons, and invoices. Verify sandbox checkout and signed provider webhooks before enabling live payment credentials.

#Separate gateway setup from readiness

Encrypted credentials, mode, callback URL, webhook secret, signature verification, negative cases, refund/cancellation expectations, and provider approval all contribute to readiness. System health should report missing prerequisites rather than hiding them.

Plans, limits, checkout, and invoices are visible to the tenant administrator. Capture details
Platform administrators provision and verify tenant boundaries. Capture details
Health checks expose production prerequisites. Capture details

#Common mistakes

  • Using live gateway credentials during documentation or demo capture.
  • Changing a plan without understanding active tenant limits.
  • Treating database connectivity as full tenant readiness.

#Verify the result

  • Platform MFA is active.
  • Tenant connectivity and migrations pass.
  • Gateway webhooks are verified in sandbox.
  • Health and commercial labels match evidence.
Enlarged documentation screenshot