Tenant configuration
PlatformConfigure tenant-specific branding, modules, policies, domains and integration settings.
Isolation
Tenant-scoped by design
Hierarchy
Organizations + sub-organizations
Access
Membership + role context
Configuration
Policies, modules & branding
Overview
Configuration is tenant-scoped and versioned. Secrets and privileged verification rules are not exposed through public configuration responses.
Configuration domains
| Domain | Examples |
|---|---|
| Branding | Name, logo references, theme tokens |
| Features | Enabled Mediloop modules and feature flags |
| Policies | Operational defaults and tenant-specific rules |
| Domains | Approved custom domains and callback origins |
| Integrations | Non-secret integration metadata and connection status |
Feature settings
PATCH /v1/tenants/{id}/configurationCopy
{
"features": {
"teleconsultation": true,
"prescriptions": true,
"remote_monitoring": false
}
}Branding & domains
Custom branding never changes Mediloop authorization semantics. Domains must be verified before activation.
Example
| Setting | Tenant override |
|---|---|
| locale | fr-LU |
| timezone | Europe/Luxembourg |
| default_currency | EUR |
| support_contact | Configured organization support desk |