Skip to main content

Multi-Tenancy

Docupath's multi-tenant architecture and what it means to work within your own instance

Multi-tenancy is the architectural foundation that ensures every Docupath customer operates within a fully isolated workspace. Each tenant receives its own logically separated environment - with independent data, configuration, users, and processing pipelines - accessible via a unique subdomain.

This architecture guarantees that no data, rules, or documents are shared across tenants, while enabling region-aligned storage for compliance with data residency requirements.


How It Works

Tenant Isolation

Each Docupath tenant is a self-contained workspace with complete logical separation from every other tenant on the platform. Tenant boundaries are enforced at every layer - application, data storage, and API access - so that one tenant's documents, users, configuration, and processing results are invisible and inaccessible to any other tenant.

Subdomain-Based Access

Every tenant is assigned a unique subdomain following the pattern yourOrganization.docupath.app. This URL serves as the single entry point for all users in that tenant. Authentication is scoped to the tenant, meaning user credentials, SSO configurations, and session tokens are valid only within the tenant they belong to.

Region-Aligned Storage

Docupath supports data residency controls that allow tenant data to be stored in a specific geographic region (e.g., EU or US). This alignment is configured at tenant provisioning and determines where documents, extracted data, and audit records are physically stored. Region alignment supports compliance with regulations such as GDPR, CCPA, and industry-specific data sovereignty requirements.


Supported Configurations and Options

Configuration

Detail

Subdomain URL

yourOrganization.docupath.app

Authentication

Email/password, Google SSO, Microsoft SSO

Data residency regions

EU, US (configured at provisioning)

Scope hierarchy for instructions, rules and output configurations

Global → Country → Organisation → Trading Party

Tenant-level settings

Branding, data retention, duplicate handling, rejection notifications


Other Technical Specifications

Parameter

Detail

Maximum users per tenant

500

Maximum organisations per tenant

100

Maximum sub-organisations per organisation

100

Data separation model

Logical isolation with access control enforcement

Storage

Region-aligned (EU/US)


Notes

  • Data residency region is set at provisioning and cannot be changed after initial setup without a migration process

  • Multi-tenancy provides logical isolation, not physical isolation - tenants in the same cloud region share infrastructure but not data

  • Cross-tenant data sharing or reporting is not supported - each tenant operates as an independent environment

  • Tenant subdomain names are unique across the platform

Did this answer your question?