For Google Workspace admins

#Why someone sees "access blocked"

Some organisations only let people sign in to third-party apps the admin has approved. When someone in such an organisation presses Connect next to Google Calendar in Veda, Google stops the sign-in and says the app is blocked or not allowed. Nothing is shared; the admin just needs to approve Veda once.

#What Veda asks for

Veda asks Google for two read-only permissions:

• See your calendar list (calendar.calendarlist.readonly) — which calendars to read.
• See events on all your calendars (calendar.events.readonly) — the meetings themselves.

Veda never creates, changes or deletes anything. The sign-in token stays on the person's computer; Veda's server never receives it or any calendar data. See Privacy.

#Approve Veda (admin)

You need the Service Settings administrator privilege.

1. In the Google Admin console, go to Menu → Security → Access and data control → API controls.
2. Click Manage App Access.
3. Under Configured apps, click Configure new app.
4. Search for Veda's client ID: 735932903208-ts2oakis6ja4rocqv0p16ur19ngsactf.apps.googleusercontent.com, and pick it.
5. For Scope, keep the top organisational unit for everyone, or choose Select org units to limit it.
6. For Access to Google data, choose Specific Google data and allow the two Calendar read-only permissions above, or choose Trusted.
7. Click Continue, then Finish.

Changes can take up to 24 hours, but usually apply sooner. After that, people can press Connect in Veda → Connections again.

#Don't want Calendar at all?

Leave Veda unapproved, or set it to Blocked. Veda's writing, memory and Ask work without any Google connection.