Learn how to use Google Console to set up a service account connection to a Calendar.

After installing Brikit Calendar Integrations, the next step is to prepare your Google Calendar so that it can be accessed by the app within Confluence. This means creating a project within the Google Cloud Platform (AKA Google Console) and setting up a service account that may access your calendar. Brikit Calendar Integrations then uses this service account to read and display calendar events.

Enable sharing in Google Workspace

If your Calendar is managed using a Google Workspace account (like most corporations using G-Suite), then turn on "external sharing" as described below. If you are connecting a personal Google Calendar or a Calendar outside of a Google Workspace account, then you may skip this step.

  • Go to https://admin.google.com

  • Navigate to Apps > G Suite > Calendar > Sharing Settings

    • Set “External sharing options for primary calendars” to the “Share all information, but outsiders cannot change calendars” option
  • Navigate to Apps > G Suite > Calendar > General Settings
    • Set “External sharing options for secondary calendars” to the “Share all information, but outsiders cannot change calendars” option

Create a project in Google Cloud Platform

Google Cloud Platform (AKA Google Console) is the interface used to control how apps connect to, and interact with, your Google tools, including Google Calendar. Here you will create a project and configure it to use the Google Calendar API.

  • Go to https://console.cloud.google.com/ 
  • Create a new project called "Brikit Google Calendars"
  • Select the existing/default Organization and Location of this account. (Or, if none are associated, select “No organization”)
  • Upon creation, click the prompt to visit the Project Page
  • In the left side-menu, navigate to APIs & Services > Library
  • Search for “Google Calendar API” and then click to select it from the results
  • Click “Enable”

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the Steps block above to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.

If using:

  1. Replace me with something to note about this how-to entry that falls outside the scope of all other sections; and
  2. Add the tight-bottom class to the next visible/non-collapsed block above this one to narrow the gap between the two blocks.
  • Replace me with a link
  • Replace me with a link
  • Aim for 4 or fewer related links.  If we need more, that's okay.  Be judicious.  Delete me when you're done.