Access and troubleshooting

Work Schedule has two access boundaries:

• module permissions govern calendars, assignments, exceptions, and effective schedule reads;
• ordinary record security governs Operational Location, Site, and Worker records and fields.

An actor may therefore have a Work Schedule permission but still be unable to select a hidden Worker or Site. Hidden records are not disclosed through assignment or schedule responses.

Setup checks

If calendar authoring is unavailable, verify that the module is enabled and its security manifest is healthy. If assignments or effective resolution are unavailable, also verify that:

• Operational Location, Site, and Worker definitions are ready;
• at least one enabled calendar has a Published revision;
• the subject has the required Site and calendar assignments;
• the Site resolves to an Operational Location with a valid IANA time zone.

Use the explicit Create, Repair, Open, and Configure access actions in Work Schedule settings. Enabling the module does not create catalogs or a default calendar.

Unresolved does not mean not working

Missing assignment, calendar, publication, location, or time-zone dependencies produce an explicit unresolved diagnostic. They are not converted into an authoritative non-working or closed answer.

During daylight-saving transitions, skipped or ambiguous wall-clock time is reported with a diagnostic. The selected-time answer remains explainable in the Site’s IANA zone.

Concurrency

Calendar mutations use the current RowVersion; assignment and exception mutations use the current chain version. Reload after a conflict. Reuse an operation id only for an exact retry after an unknown outcome.