One product. Clear company boundaries.
A customer owns its debt settlement business; RomyLabs operates the CRM platform. That distinction should remain clear in branding, administration and permissions. The planned architecture uses a dedicated SettleLift product database with isolated company tenants and office records inside each company.
Put access behind every team workflow.
- Create the company identity and office structure. Keep customer business ownership separate from the protected platform administrator mapping.
- Assign staff roles and case responsibilities. A user’s editable profile should never grant access to another office or promote the account to platform administrator.
- Review the company’s state service scope and provider configuration. Invite staff and clients only after the tenant’s actual authentication and storage boundaries are verified.
What stays connected
Separate company membership from individual roles and assigned cases. Staff, clients and invited creditor representatives need different views. Access boundaries must be verified with real accounts before anyone is invited into a live workspace.
Current scope & remaining work
What you can explore today.
- Working preview
- Office architecture display, planned roles, company-state review controls and product branding.
- Prepared backend
- Tenant RLS, private platform mapping and assignment-scoped record access.
- Connection work remaining
- Live company provisioning, invitations, office administration and Admin Portal connection.
Does each office need its own CRM product database?
The planned model is one dedicated Supabase project for SettleLift, with isolated customer companies and their offices inside it. Other RomyLabs CRM products remain separate. Real provisioning is not active yet.