Access & data approach
The current application is a development preview for synthetic data. Do not enter real client records. Local schema tests do not certify production configuration or connected services.
Company isolation
The prepared foundation separates records by tenant and keeps record relationships within that tenant. Local tests exercise cross-company access, staff assignments and denied privilege escalation. The real Supabase project still needs configuration and verification.
Client access
The prepared portal API identifies the authenticated user and returns only cases linked to that account. It omits internal notes, staff drafts and unshared documents. The visible application remains a staff simulation and does not authenticate real clients.
Documents and evidence
The prepared model uses private storage and explicit access for shared documents. Unsigned worksheets preserve their generated data. E-signatures, file verification and production audit evidence still require integration and complete testing.
Financial boundaries
Balances, deposits and holds in the preview are hypothetical. The prototype does not hold or transfer money. Prepared payment and financial-evidence tables do not permit direct writes from ordinary authenticated users.
What remains before release
Verify real authentication and storage, complete server workflows, test concurrency and failure recovery, connect authorized providers, review enrollment documents, and complete mobile and end-to-end checks. No security or regulatory certification is claimed here.
YOUR OPERATION. YOUR NEXT STEP.Let’s talk through your workflow.
Discuss your team, current tools and priorities with RomyLabs. SettleLift is in development; pricing and availability are not yet announced.
Talk to RomyLabs ↗