To use Buzz, you "Sign in with Google." Buzz never sees or stores your Google password. We’ve carefully chosen the scope of requested access to the minimum. All following permissions are required for you to work with your calendar in Buzz:

Screenshot 2022-07-28 at 12.04.53.png

How does Buzz handle Google Login and Calendar Data?

When connecting a Google Calendar account to Buzz, we request read access to your calendar. Read access is needed to display your calendar events and make suggestions based on emails of attendees of the events. The event data are not stored in the database but cached in the server. This data is refreshed every two minutes.

Buzz is verified by Google to utilize OAuth API verification and does not access any user data categorized as "restricted."

<aside> 👉 Read next: Connect Buzz to Slack

</aside>

<aside> ☝ Related: Google Calendar

</aside>

<aside> 💡 Troubleshoot: Error when signing in with Google “Buzz needs access to your calendar to show your schedule.”

Screenshot 2022-12-02 at 11.54.18.png

****If you see this message you likely didn’t approve Calendar read access during the sign in process. Make sure to tick the checkbox allowing Buzz to read calendar events in the second step of the sing in process, and you’ll be signed in smoothly.

</aside>

<aside> 💡 Troubleshoot: Error when signing in with Google “We couldn’t find an invitation for your account”

Screenshot 2022-12-02 at 11.55.44.png

****If you see this message when signing in with Google, you’ve likely tried signing in with a personal gmail account which has not been invited to a workspace. Unless you’re signing up with a work e.mail you’ll need to have received a personal invite to get access to Buzz. Ask the team you’re joining for an invitation and then try signing in again.

</aside>

Any further questions about permissions or getting started? We're excited to answer, contact [email protected]

Links