What is a tenant, and why does it matter?
Practice this questionDiscussion template: use your own project facts, ownership, and measured outcomes. Bracketed text is a placeholder.
Short explanation:
A tenant is an organizational identity boundary containing users, applications and policies. Multi-tenant applications must decide which organizations can sign in and which data each organization may access. Identity-provider tenant validation and application database tenant scoping are related but separate controls.
Key points:
-
A tenant is an organization's identity directory/boundary.
-
Decide which tenants may sign in and validate that rule.
-
Login alone does not grant access to another organization's records.
-
Include tenant context in queries and caches where data is tenant-specific; do not trust a body field as authority to switch tenants.
Interview point:
- A valid external login does not by itself authorize reading another organization's employee records.
Adapted from 10_RESUME_PROJECT_DEEP_DIVE.md · “What is a tenant, and why does it matter?”. Code examples are study fragments. Difficulty and core labels are editorial estimates; version-specific behavior should be checked against your project.