Clinic services that move with you
Your workspace owns AI access, members, usage, and its WhatsApp channel. Switching standalone, on-prem, or cloud does not change the services account.
Open Services and activate with your existing clinic administrator. Staff continue using their normal clinic accounts—no extra account, email setup, or new password.
Use password, Authenticator, or recovery code
ESCAI Services
What follows the workspace
Clinic data stays separate
Standalone, on-prem, and cloud remain choices for clinical data. This services account only governs central AI and WhatsApp access.
No provider secrets on clinic devicesDeployment binding
Changing deployment mode is intentionally read-only here until the target connector is healthy and the handoff can be fenced safely.
| Staff | Assistant | Clinical | Voice | Manage |
|---|
Not started
Owner memberships cannot be edited or removed here. Disabling or removing a member immediately revokes that member’s devices and refresh-token families.
| Name | Role | Status |
|---|
| Window | Requests | Tokens | Cost |
|---|
| Time | Action | Outcome |
|---|
Session security
Owner email sign-in uses a short-lived, single-use link and a secure browser cookie. Authenticator remains an optional fallback. Native devices use short-lived RS256 access tokens, rotating refresh tokens, and DPoP-bound keys.