Platform and tenant administrators
Prove the first workspace is usable before connecting live systems
A successful login is not enough: it must resolve the correct workspace and permissions. FlowOS keeps platform administration separate from tenant work. Verify both contexts before inviting users or publishing automation.
Before you start
- The installer is locked.
- Central and tenant migrations completed.
- The first administrator account is available.
#Sign in to the intended tenant
- Open the tenant login URL.
- Enter the workspace slug, administrator email, and password.
- Complete email, OTP, or TOTP challenges when policy requires them.
- Check the workspace name and navigation after redirect.
- Sign out and verify that the same email in a different workspace does not grant access.
#Complete onboarding in dependency order
Start with identity and branding, then people and roles, mail delivery, backup policy, capture forms, workflows, connectors, developer keys, and billing. Optional AI, voice, payment, and provider features should remain disabled until their prerequisites are proven.
#Know where evidence appears
The dashboard summarizes the tenant context. Use the left navigation to reach workflow runs, approvals, integrations, leads, projects, developer tools, settings, notifications, and activity logs. When something appears missing, first check the workspace, role, plan, and feature readiness—not the database.
#Common mistakes
- Confusing platform administrator access with tenant administrator access.
- Inviting users before roles are reviewed.
- Enabling providers before callbacks, workers, and secrets are ready.
#Verify the result
- The administrator reaches the intended workspace.
- A wrong workspace does not authenticate the same user.
- Onboarding shows no unexplained critical blockers.
- The queue and scheduler plan is active.