Onboarding
Onboarding legal readiness
DEV-visible legal checkpoint for new workspace and customer onboarding.
Last updated: June 29, 2026
Legal review required before PROD
Draft for DEV validation only. This is not legal advice. Requires review and acceptance by a qualified lawyer before any PROD publication, checkout, onboarding, sales proposal, App Store submission or customer contract use.
Onboarding status
Public self-serve registration is visible on DEV. This page gives the new-customer onboarding flow a visible legal checkpoint without changing customer data.
Before PROD onboarding for paying customers, users should see the accepted Terms, Privacy Policy, AI Disclaimer, Acceptable Use Policy, support route, data deletion route and billing/credit rules.
Workspace owner responsibilities
Workspace owners should confirm they have permission to add users, connect third-party services, upload knowledge-base data and process customer conversations in Max AI.
Onboarding should explain that AI output needs human review and that connected automations remain the responsibility of the workspace owner.
Legal acceptance to capture
Before paid onboarding, Max AI should record who accepted the final policies, for which workspace, at what time, from which signup or checkout surface, and which policy versions were accepted.
Workspace owners should confirm business-use scope, connected-service permissions, end-user notice responsibility, AI-review responsibility and billing/credit rules.
Paid customer readiness
A new paying workspace owner should understand plan limits, AI-credit allowance, overage position, invoice route, cancellation route, refund route and support expectations before activating live billing.
If Max AI stays B2B-first, onboarding should ask the workspace owner to confirm business authority and buyer details before payment or immediately after signup.
Customer-facing AI use
If a workspace uses Max AI in a public widget or connected channel, onboarding should remind the owner to provide appropriate notices to end users.
High-impact, regulated or automated decision use should stay disabled unless separately reviewed and approved.