Tenant
An isolated Papyrus instance for one organisation — with its own users, documents, settings, billing, and data residency.
Tenant
A tenant is an isolated Papyrus instance for one organisation. Multi-tenancy means many organisations share the same Papyrus platform infrastructure while remaining logically separated — one tenant's users, documents, and data are never visible to another tenant.
Each tenant has:
- Its own users, roles, departments
- Its own folder hierarchy and document store
- Its own configuration (classifications, retention policies, workflow templates)
- Its own subscription plan and billing
- Its own branding (logo, colours, custom domain on Business+)
- Its own audit log
- Its own encryption keys
Tenants are identified by a slug (e.g., acme.papyrus.io) and can optionally use a custom domain (docs.acme.co.ke). Tenant resolution happens on every request — Papyrus inspects the subdomain, custom domain, JWT, or X-Tenant-Id header.
Within Papyrus.io's hosted service, a tenant is a logical isolation, not a physical one. Enterprise customers can opt for dedicated infrastructure.