Configure calendar settings and permissions

Modified on Mon, 20 Apr at 12:02 PM

For: Superusers, recruiters, hiring managers

 

What you’ll achieve

Configure default calendar behaviour and control user permissions for booking and visibility.

 

I want to:

  • Set default calendar values
  • Configure email defaults
  • Control booking cut-off restrictions
  • Allow private events
  • Manage booking permissions by security role

 

Configure default calendar settings

Some fields in event setup can auto-populate based on System Customisation.

 

Go to: Settings > System Customisation > Calendar

  • From here you can configure:
    • Default invite status
    • Default email templates

 

A screenshot of a computer

Description automatically generated

 

To check the default post-booking status:

Settings > System Customisation > Customise > Interview Statuses > Interview Accepted


Select Save after making changes.

 

Configure booking cut-off override

By default, users cannot book candidates beyond the event’s booking cut-off restriction.

 

To allow specific roles to override this:

  1. Go to Settings > Security Roles.
  2. Open the relevant role.
  3. Go to the Calendar tab.
  4. Next to: Calendar Entries – Ignore booking cut off restriction
    • Enable:
      1. Access
      2. Add
      3. Update
  5. Select Save.

 

A screenshot of a computer

Description automatically generated

 

Allow users to create private events

To allow users to create private events:

  1. Go to Settings > Security Roles.
  2. Open the relevant role.
  3. Go to the Calendar tab.
  4. Enable Is Private.
  5. Select Save.


Best practice
- Limit booking cut-off overrides to trusted roles.
- Restrict private event permissions where audit visibility is required.
- Pre-set email templates to reduce setup errors.


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