Skip to main content

Multi-Tenancy Isolation

The HR COREHub platform is architected with strict multi-tenancy controls to ensure partition isolation and data privacy.

Tenant Architecture​

Each customer organization is mapped to a distinct logical Tenant.

  • Data, configurations, and user structures are strictly isolated within each tenant partition.
  • It is impossible for users in Tenant A to access, query, or view data from Tenant B.
  • System configurations, database queries, and storage buckets utilize tenant-specific keys to ensure physical or logical division.
Diagram illustrating the multi-tenancy database isolation and secure routing layers of the HR COREHub platform

Tenant Selection​

  • During Login: Users must input or select their specific Tenant Identifier (usually matching the corporate domain) before typing their passwords.
  • SSO Mappings: Single Sign-On (SSO) configurations are automatically determined based on your tenant selection.