How can an admin restrict employees from raising permissions or regularizations during leave or when no swipes are recorded?

Created by Product Content Team, Modified on Wed, 18 Jun at 1:57 PM by Product Content Team


In many organizations, employees have the flexibility to raise permission or regularization requests to adjust their attendance. However, there may be instances where employees on leave or with invalid swipes (no swipes) unintentionally use this feature, which can occasionally result in discrepancies in attendance records and approval processes.

To address this, as an admin, you can restrict employees from raising permissions or regularizations during leave or when no swipes are recorded.

To do so, from the greytHR Admin portal, go to Workflow > Setup Workflow Levels.

  1. Check the Workflow Type as Regularization & Permission

  2. Click View Details > Workflow Policy.

  3. Go to Restrict employees based on their attendance status option.

  4. Configure Restrict permission applications for the entire day rules:

  • Select the rule for restricting permission applications based on attendance status. Choose between:

    • If both session statuses match the configured status (for example, both morning and evening sessions are Leave or No Swipe).

    • If any one of the session statuses matches the configured status (for example, either the morning or evening session is Leave or No Swipe).

  1. Set Attendance Status/No Swipe conditions as:

  • Leave

  • No Swipe

  1. Fill out the other details as required.

  2. Click Save Policy > Review and Submit

This ensures that employees can only raise requests when they meet the proper attendance conditions.


Looking for More Support?

Find answers and insights across our resources. Refer to our detailed Knowledge Base for in-depth articles, explore our practical video guides, and stay informed with our latest product updates.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article