# Schedule Settings ### **Overview** Within this tab, admin users can set the module **Label** as well as manage the Off-Shift Access restrictions. **Break** inclusions can also be enabled from this menu.
*** ### Setting Retention Policies Admins control how far back employees can submit attestations using the **Retention Period for Past Shifts Data** setting. This defines the number of past weeks that remain accessible, excluding the current week. The default retention is three weeks, though you can configure it to range from one week to six weeks, or disable it entirely. Every Sunday, the system permanently deletes shift data older than the configured period, while the current week’s data is always preserved. This ensures that historical records remain consistent with company policy and compliance requirements. *** ### Off-Shift Access Restriction MangoApps allows admins to restrict platform access for employees **outside of scheduled shift hours** or **outside assigned office locations** (using geofencing). These restrictions ensure organizations comply with labor laws and overtime regulations, prevent unauthorized work, and align with in-office mandates. Employees can still request access by providing consent, ensuring flexibility while maintaining compliance. In the **Restrict Off-Shift Access** section, configure the settings.
#### Admin Configurable Options **User Segment:** Target specific groups (static or dynamic segments) who should have off-shift restrictions. **Buffer Time:** Grace period around scheduled shifts (default 10 minutes before and after). **Require Consent:** Enable/disable the consent prompt and customize its message. **Navigation for Off-Shift Users:** Define a restricted version of platform navigation for off-shift users. {% hint style="success" %} Access to content still depends on user permissions and is not blocked. {% endhint %} {% hint style="warning" %} Notifications continue as per user preferences, even during restricted access. {% endhint %} #### End User Experience MangoApps checks the user’s login time against their scheduled shift (plus/minus a configured buffer time). If the user is **within shift hours**: Full navigation access is granted based on the user's permissions. If the user is **outside shift hours**: The user sees a customizable **Consent Prompt** (if enabled and configured). Upon consenting, they gain **limited navigation access** as defined by the admin. **Consent Expiry:** Consent must be re-confirmed if the user remains logged in and off-shift for more than 1 hour.
#### Supported Shift Data Sources: * Kronos * UKG * PDI Workforce * Spectrum\ \&#xNAN;*(Custom shift data sources are not supported.)* {% hint style="info" %} Consent logs can be viewed from **Admin Portal > Home > Logs > Restricted Access Consent Logs** {% endhint %} *** #### Best Practices For Access Restriction * Clearly communicate restricted access policies to employees to avoid confusion. * Regularly review user segments and shift/location assignments to ensure restrictions are applied correctly. * Customize consent prompts with specific language to match legal and compliance requirements. * Periodically review consent logs for audit and compliance tracking. *** #### See This Feature in Action Watch the video below to see how access restrictions work in **Shifts & Schedules**. {% embed url="" %} *** ### Enabling the Attestation Feature The attestation feature in the Schedules module allows organizations to capture accurate shift data directly from employees, ensuring compliance and reducing discrepancies. As an admin, you are responsible for enabling, configuring, and maintaining this feature so that employees can review their shifts, confirm actual hours, and record unscheduled work when necessary.
To activate attestation, go to **Admin Portal > Schedules > Settings** and turn on the **Enable Attestation** option.
Once enabled, you may decide whether all users have access to attest their shifts or whether it should be limited to a specific user segment. Only one segment can be chosen, which ensures precise control over which employees participate. An attestation tracker **must** be linked during setup. This tracker is the system’s official record of all attestations and can either be an existing tracker or a newly created one. It **cannot be deleted**, but it may be archived if no longer in use. *** #### Configuring the Attestation Tracker The attestation tracker is where all shift confirmations are stored. If you have already created a tracker, select it from the field then proceed to the **Column Mapping** step. If you do not have a tracker prepared, click the **Create attestation tracker** button to quickly create one in the moment.
Each record includes essential details such as the employee ID, shift ID, start and end times, location, and the type of shift segment (regular, transfer, or break). Additional optional fields are available to capture shift work type, shift origin, and employee notes. A unique Shift ID is generated automatically by combining system identifiers from the scheduled shift. Once data is saved in the tracker, **it is locked by default** to preserve compliance and accuracy. If the tracker is archived, past attestation records remain visible in the Schedules module.
*** #### Customizing the Attestation Message Part of the attestation flow includes a confirmation statement shown to employees before they submit their shift details. As an admin, you can create and customize this message to align with company policy. The text can be up to 500 characters, and it must be completed before the attestation setup is saved. Employees are required to acknowledge this message before submission, ensuring that all attestations carry an explicit confirmation. *** #### Adding Shifts Outside the Schedule By enabling attestation, admins also allow employees to record shifts that do not appear in their assigned schedules. When enabled, eligible employees can add past or current shifts, provide their times and location, and attest to them immediately. These records are added to the attestation tracker just like regular attestations and are marked as attested in the schedule view, ensuring consistency between scheduled and unscheduled work records. *** #### Monitoring Pending Attestations The **My Priority Items** widget in MangoApps gives admins and employees visibility into which shifts remain un-attested.
Past shifts eligible for attestation automatically appear here until they are completed or until they expire based on the retention policy. Once submitted, the item is removed from the list, helping ensure timely and complete attestations across the workforce. *** #### Exporting and Reporting All attestation data can be exported for auditing, reporting, or payroll purposes. Exports are available in CSV format for detailed raw data and in PDF format for a simplified visual overview. This flexibility supports both compliance reviews and operational reporting. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://guides.mangoapps.com/admin-guide/module-settings/schedules/schedule-settings.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.