Role-appropriate workspaces
Account roles and permissions govern the actions available in the application. Clinic, branch and patient context apply to the relevant workflows.
Defined access.
Considered boundaries.
A connected platform does not mean unrestricted access. Learn how the application separates public information from clinical workflows.
A deliberate public boundary
The directory lists eligible, approved clinics that opt in. Public pages do not publish patient records, internal clinical notes or private staff directories.
Account and request controls
Existing session handling, CSRF protection, request validation and configured two-factor authentication remain part of the application.
Branded domains, separate access
Verified custom clinic domains serve the clinic website and booking experience; they do not expose platform sign-in or administrative screens.
Records are not demo content
The public product preview uses illustrative data. Interactive preview selections stay in the page and do not create or update clinical records.
Configuration still matters
Hosting, HTTPS, account administration, backup testing, retention policies and applicable legal requirements remain the operator's responsibility.
Software controls are not a compliance certification.
This page describes application behavior. It does not certify regulatory compliance, guarantee security, replace legal advice or describe a hosting provider's policies. Before using real patient data, the operator should verify the deployment, access controls, backup recovery and relevant obligations.
YOUR NEXT CHAPTERMake room for
Make room for
better-connected care.
Bring your practice into one considered workspace.
Start your clinic
Already part of Rumi? Sign in
Registration is subject to email verification and approval.