Access controls
Owner, attorney, staff, and viewer roles are checked server-side before dashboard actions.
Security
Security and account protection
Legal Growth OS is built around tenant-scoped access, role permissions, protected forms, verified workflows, and production configuration checks.
Plain answer
Security starts with tenant boundaries
Customer data must stay inside the tenant account it belongs to. Dashboard roles, server-side permissions, and scoped queries support that boundary.
- Tenant-scoped records
- CSRF and session protection
- reCAPTCHA on public account flows
- No cross-tenant AI data access
Protected public forms
Email validation, phone normalization, reCAPTCHA, honeypot fields, consent language, and safe redirects reduce abuse.
Operational checks
Production readiness commands check static files, environment separation, Stripe mode, database connectivity, and security settings.
Questions
Common questions
Does this page replace a security audit?
No. It summarizes the platform posture and should be paired with operational review before launch.
Can support see tenant data?
Access should be limited to authorized operational needs and audited where support workflows require it.