DeskGate practical help

Working Schedules and Endpoint Rules

Keep work-time definitions, group assignments and endpoint policies aligned with the team they are intended to serve.

Define scope

Verify configuration

Review the result

Before You Begin

Describe the configured working periods; meetings and offline work still require context in activity review.

Connect the intended people and devices with the relevant administrative rules.

The correct group receives the intended policy during the expected period, and reports are interpreted using the same working context.

Identify the team’s intended working hours and the policy that depends on them. Separate scheduled work from assumptions about productivity.

Use the working-time group and its related definitions to check the hours required for that team.

Review the group and policy selections that reference the work time. A schedule definition alone does not establish that every endpoint uses it.

Test an appropriate device inside and outside the intended period. Check the corresponding policy and report context before wider rollout.

Check the selected schedule, local time settings and the effective group/rule association.

Review actual group membership and overlapping rule assignments before changing the schedule.

Confirm the work window and discuss calls, meetings and other work outside computer interaction.

Does a work schedule prove attendance?

No. A configured schedule is a reference. Attendance records, where integrated, come from their own source.

Are time rules shared by every feature?

Confirm the schedule selection exposed by the specific policy or report; do not assume a global setting applies everywhere.

Where should we begin?

Use one representative team and a clear, observable rule before expanding the configuration.

Bring your device scope and the question you want to answer. Review the relevant capabilities in a guided demo.