Multi-tenancy & Sectors
How sector and domain isolation works, and why it fails closed by default.
AgnoHire isolates data using a sector as the primary tenancy boundary, with an optional domain as a sub-grouping inside it.
Sectors
A sector typically represents a business unit, subsidiary, or brand operating inside one AgnoHire deployment. Every job requisition, candidate, and interview belongs to exactly one sector.
Domains
A domain is an optional taxonomy inside a sector — useful when a business unit itself has internal divisions (by skill area, geography, or however your organization actually structures hiring).
Fail-closed by default
This is the part that matters most: a non-admin user with no sector assigned matches nothing, not everything. Unscoped access is treated as zero access, never as unrestricted access.
Every scoped database query combines sector (and domain, where relevant) using AND, never OR — a deliberate choice, since an OR-based scope check is a well-known way to accidentally leak data across tenants.
Who can see what
- Super Admin bypasses sector scoping entirely (by design, for platform administration).
- Admin / HR / Recruiter / Hiring Manager are scoped to their assigned sector(s).
- Candidates only ever see their own record, regardless of sector.
