Multi-Tenancy Configuration¶
When to use this page¶
Use this guide when you need to:
- enable tenant-aware behavior by domain,
- map hostnames to tenant configuration,
- validate data and content isolation across tenants.
Tenant resolution model¶
SkyCMS resolves tenant context from incoming host/domain information and uses that context for settings, content access, and publishing behavior.
Required settings¶
- tenant domain entries,
- per-tenant configuration records,
- provider settings valid for each tenant.
Domain mapping¶
Recommended mapping approach:
- define canonical domains per tenant,
- map each domain to tenant configuration,
- validate redirects and host-header behavior.
Testing tenant isolation¶
Validate with at least two tenant domains:
- each domain resolves the expected tenant,
- content/settings do not leak between tenants,
- publish and cache purge actions affect only intended tenant assets.
Troubleshooting¶
- wrong content by domain: verify domain-to-tenant mapping and proxy forwarding headers,
- shared settings unexpectedly: verify tenant key usage in configuration queries,
- publish affecting another tenant: verify isolation in publish and storage paths.