{"id":8741,"date":"2025-07-21T17:40:07","date_gmt":"2025-07-21T17:40:07","guid":{"rendered":"https:\/\/learn.brightbreaks.com\/learn\/knowledge\/bright-breaks-calendar-integration\/"},"modified":"2025-07-21T17:40:07","modified_gmt":"2025-07-21T17:40:07","password":"","slug":"bright-breaks-calendar-integration","status":"publish","type":"docs","link":"https:\/\/learn.brightbreaks.com\/learn\/knowledge\/bright-breaks-calendar-integration\/","title":{"rendered":"Required Calendar Permissions for Daily Break"},"content":{"rendered":"

Download the PDF version here<\/a>. <\/h3>\n

Overview<\/h3>\n

Bright Breaks allows users to connect their Outlook & Google calendar for the purpose of filtering out breaks that conflict with events in their calendar. The same mechanism is used by the \u201cDaily Break\u201d feature where short breaks are recommended to users based on free time in the users\u2019 calendars.<\/p>\n

How Permissions Are Given<\/h3>\n

To connect their calendar, the user follows an OAuth 2.0 flow to consent to a limited set of permissions.<\/p>\n

Bright Breaks requires the user to consent to \u201coffline access\u201d, i.e. providing Bright Breaks a refresh token so that Bright Breaks\u2019 server can read the required info from the user\u2019s calendar at any time unless and until the user revokes permission. The user can revoke this permission at any time through their Bright Breaks settings at brightbreaks.com\/client\/settings (or directly through their Outlook or Google account).<\/p>\n

Aside from the refresh token and the email address associated with the calendar, information about a user\u2019s calendar is never stored on Bright Breaks\u2019 servers.<\/p>\n

Outlook Calendar Permissions<\/h3>\n

In order for Bright Breaks to be able to determine when a user has free time, we require the Calendars.ReadBasic permission (see https:\/\/learn.microsoft.com\/en-us\/graph\/permissions-reference#calendarsreadbasic<\/a>). This allows Bright Breaks to read events in user calendars, except for properties such as body, attachments, and extensions. The only information we use is when events in the user\u2019s calendar begin and end in order to determine when a user is available to take a break.<\/p>\n

In addition, we require the User.ReadBasic.All permission (see https:\/\/learn.microsoft.com\/en-us\/graph\/permissions-reference#userreadbasicall<\/a>). We use this only to retrieve the email address associated with the calendar being connected, since this is a parameter that is necessary when determining calendar availability.<\/p>\n

In order for integration permission to be granted on Outlook, an Admin Outlook user needs to:<\/p>\n