View and manage configured exceptions

Once Web and Mobile Attendance Exceptions or Default Attendance Status Exceptions are configured, they appear on the Attendance Exception page as saved rules. Administrators can review these rules at any time, and edit or remove them as organizational needs change.

This article is meant for administrators who want to review, update, or delete existing exception rules.

When to use this

Reviewing and managing exceptions is useful in the following situations:

1. Periodic audits to check whether existing exception rules are still relevant and correctly configured.
2. Role changes, where an employee moves to a different department or designation and their earlier exception is no longer valid.
3. Organizational restructuring, such as a branch closure, entity merger, or team reorganization.
4. Location changes, where a specific site adopts different attendance rules than before.
5. Employee exits, where exceptions tied to individuals need to be removed after separation.

Step-by-step instructions

Navigation Path: Control Panel → Settings → Attendance → Configure Attendance

To open the Attendance Exception page, click any of the Configure Exception links on the Configure Attendance page. These links are available in three places: next to Default Attendance Status, under Web Attendance, and under Mobile Attendance. All three links open the same Attendance Exception page.

Step 1: Review Configured Exceptions

The Attendance Exception page shows all configured rules across two sections:

1. Web/Mobile Exceptions. Displays both group-level and employee-level channel exceptions in separate tables.
2. Default Attendance. Displays both group-level and employee-level default status rules in separate tables.

Each table shows the relevant filters (Department, Designation, Location, Entity, or Employee), the configured value (Modules for channel exceptions, or Status for default rules), and an Actions column with icons for editing and deleting.

If you have a large number of exceptions, you can use the Search box above each table to quickly locate a specific rule, or change the entries per page dropdown to display more rows at once.

Step 2: Edit an Exception

1. Locate the exception you want to update in the relevant table.
2. Click the edit icon in the Actions column for that row.
3. Update the required fields in the form that appears.
4. Click Save to apply the changes.

The updated rule replaces the earlier version in the table.

Step 3: Remove an Exception

1. Locate the exception you want to remove in the relevant table.
2. Click the delete icon in the Actions column for that row.
3. A confirmation prompt appears. Click Yes to confirm the deletion.

Once confirmed, the exception rule is removed. The affected employee or group immediately falls back to the next applicable rule in the priority order (group-level rule, or company-level setting if no group-level rule exists).

Related configurations

1. Configure Web and Mobile Attendance Exceptions. Create new exception rules for Web or Mobile Attendance channel access. Refer to Configure Web and Mobile Attendance Exceptions.
2. Set Default Attendance Status Exceptions. Create new exception rules for default attendance status (Present or Absent). Refer to Set Default Attendance Status Exceptions.

Where it reflects

Once an exception is edited or removed:

1. The change takes effect immediately for the affected employees.
2. Channel access changes reflect in the mobile app and web portal shortly after. In some cases, the affected employee may need to log out and log back in for the changes to appear.
3. Default status changes apply from the next attendance cycle for any day the employee has not already punched.

Important notes

1. When an exception is removed, the affected employee or group falls back to the next applicable rule in the priority order (group-level rule, or company-level setting).
2. Exception changes take effect immediately after saving or deletion. In some cases, the affected employee may need to log out and log back in for the updates to appear.
3. Before deleting an exception, ensure the rule is genuinely no longer required. Once deleted, a rule cannot be restored, and needs to be configured again through the standard exception setup.