hora Calendar for IT admins.

How to allow hora Calendar for users in your Google Workspace organization, and what access it asks for.
Google Workspace · OAuth app access

How hora accesses Google data

hora Calendar is a native app for Mac. It talks to Google APIs directly from the user's device with OAuth 2.0 and PKCE. Calendar data is cached locally on the device. It is not stored on hora servers. hora's OAuth app is verified by Google for the scopes listed below.

Allow hora in the Admin console

If your organization restricts third-party apps, users see an error when they sign in to hora. A super admin can allow the app:

  1. In the Google Admin console, go to Security → Access and data control → API controls.
  2. Click Manage App Access, then Configure new app.
  3. Search for hora Calendar and select it.
  4. Choose the organizational units that should have access, or keep the top-level unit for everyone.
  5. Set Access to Google data to Trusted, then click Finish.

If hora does not appear in the search results, ask us for the OAuth client ID through the support form and search by client ID instead. Google says changes can take up to 24 hours, but they usually apply sooner. For details, see Google's guide Control which apps access Google Workspace data.

Limited access is enough only if Calendar, Contacts, and Tasks are unrestricted in Manage Google Services. If any of those services is restricted, hora needs Trusted access.

OAuth scopes hora requests

All scopes start with https://www.googleapis.com/auth/ except openid, email, and profile.

  • calendar — Read calendars and create, edit, delete, and respond to events.
  • calendar.settings.readonly — Read Calendar settings such as time zone, week start, and working hours.
  • contacts.readonly, contacts.other.readonly — Suggest people when adding guests to an event.
  • directory.readonly — Suggest colleagues from your organization's directory when adding guests.
  • admin.directory.resource.calendar.readonly — List meeting rooms and other bookable resources. Read-only.
  • tasks — Show and edit Google Tasks next to events.
  • openid, email, profile — Identify which Google Account is signed in.

hora does not request Gmail or Drive access.

Sign-in errors your users may report

  • "Access blocked: hora Calendar's request is blocked by your admin" or Error 400: admin_policy_enforced— the app is blocked or not configured for that user's organizational unit. Follow the steps above.
  • Sign-in works, but some data is missing — a Google service such as Tasks or the shared directory is turned off or restricted for that user. hora keeps working with what the user can access.

Need help?

Write to us through the support form. Include your Workspace edition and the exact error text. Please do not send tokens or screenshots with private calendar data. For how we handle data, see the Privacy Policy.