Skip to main content

Authorization

Audience​

Developers, QA engineers, support engineers, security engineers, solution architects, and implementation partners.

Reference Content​

This page records source-verified Workforce Scheduling API behavior and boundaries.

Summary​

Named Attendance policies are registered, but each currently requires only an authenticated user. None of those named policies is applied to scheduling endpoints.

Native surface​

Native reads and mutations have no verified role or permission checks. Tenant context is required by application services, but tenant resolution is not authorization.

Compatibility surface​

Authenticated callers without either supported administrative role are denied for shift, weekly-off, and policy mutations. Unauthenticated callers are not denied by that helper. Compatibility reads have no role checks.

The legacy monolith controllers require authentication for the whole controller and administrative roles for mutations. The extracted compatibility surface therefore does not reproduce the monolith authentication boundary.

Frontend controls​

The client route and menus require configured modules, permissions, and HR-oriented roles. Those controls affect visibility and navigation only.

Classification​

Authorization is Partial on compatibility mutations and Not implemented for native scheduling routes. Least-privilege production policies require confirmation.

Source References​

  • microservices/src/attendance-service/Program.cs
  • microservices/src/attendance-service/Api/Endpoints.cs
  • microservices/src/attendance-service/Api/ShiftPolicyCompatEndpoints.cs
  • Controllers/ShiftsController.cs
  • Controllers/WeeklyOffsController.cs

See Also​

Keywords​

  • Workforce Scheduling API
  • Shift endpoints
  • Attendance policy API

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-20
  • Next review: 2026-10-20