Helpdesk API Tenant Context
Audience
Developers, security, QA, support and architects.
Summary
Tenant enforcement combines HttpTenantContext with EF Core global query filters. It is separate from authentication and authorization.
Reference Content
Create operations that originate tenant-owned roots call a positive-tenant requirement. Existing-ticket mutations rely on tenant-filtered entity lookup. Read operations generally do not require a tenant explicitly; missing context resolves the query filter to tenant zero and normally returns no tenant entities.
Audit and timeline are filtered. The outbox diagnostic set has no tenant query filter. Super-administrator context bypasses tenant-entity and activity filters. Employee gateway forwarding does not add requester filtering.
Requires confirmation
Trusted tenant source, missing-tenant response policy, outbox isolation, super-administrator access and requester-level filtering require confirmation.
Source References
microservices/src/helpdesk-service/Application/Common.csmicroservices/src/helpdesk-service/Infrastructure/HelpdeskDbContext.csmicroservices/src/helpdesk-service/Api/HelpdeskEndpoints.csmicroservices/src/gateway-api/EssEndpoints.cs
Related Articles
See Also
Keywords
Tenant context, global query filter, tenant enforcement, outbox isolation.
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Next review: 2026-10-20