Feature Flags

Summary

This page records verified Workforce Scheduling UI and operational behavior and identifies unsupported capabilities explicitly.

Audience

Business users, developers, QA engineers, support engineers, solution architects, and implementation partners.

Reference Content

Three distinct gating mechanisms are verified:

Gate	Purpose	Behavior
Client module feature	Controls the Time Office navigation and route	Missing entitlement hides or denies the UI
Client permission features	Controls shift/settings access	Any accepted permission grants the route rule
Gateway scheduling cutover	Selects the backend owner for shift and weekly-off compatibility routes	Defaults to the legacy owner until enabled

Attendance-policy routing is explicitly claimed by the scheduling slice when cut over. The broader Attendance routing toggle is independent.

The Integrations & Features administration page displays feature strings returned by the current session but is read-only. No user-facing control changes the gateway cutover, and no per-screen experimental flag was found in Shift Management.

Infrastructure configuration identifiers are intentionally omitted from this public documentation.

Source References

• UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
• UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
• UI/salary-ui/apps/client-hrms-portal/src/pages/admin/OperationsAdminPages.tsx
• microservices/src/gateway-api/Program.cs

Related Articles

• UI and operations overview
• Known limitations
• Source map

See Also

• Events documentation
• API documentation
• Technical documentation

Keywords

• Workforce Scheduling UI
• Shift administration
• Scheduling operations

Revision Information

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