Admin consent — what it grants

When Hubhus is approved, it receives permission to:

• Read and write calendar events via Microsoft Graph
• List calendars and their owners in your organization
• Import, export, and keep events in sync

Hubhus only syncs calendars you explicitly link — all other calendars are ignored even if technically accessible. To check or update admin roles: admin.microsoft.com

Import, Export, and Two-way sync explained

Import (Outlook → Hubhus): Hubhus imports events for the current month + 1 year forward. Microsoft notifies Hubhus of changes in near real-time. If import is disabled, all imported Outlook events are permanently removed from Hubhus.

Export (Hubhus → Outlook): New Hubhus events are pushed to Outlook. Updates in Hubhus update the Outlook event. If export is disabled, no further Hubhus events are exported (already exported events remain).

Two-way sync: Both enabled — edits in either system update the other. Deleting a Hubhus-created event deletes it in Outlook. Hubhus never deletes Outlook-native events from Outlook.

Privacy and access control

• Only explicitly linked calendars are synced
• Individual calendars can be marked as Private — event details are hidden in Hubhus, but time blocking remains active
• Booking availability respects private events even without showing their content

Troubleshooting

Missing calendars: New Outlook mailbox not synced yet or list outdated → Refresh list of available Outlook calendars → re-link.

Permission errors: Admin consent not granted, wrong role, or Hubhus user email doesn't match Outlook mailbox → Ensure correct role → re-run activation → refresh list.

Event errors: Resource not linked to a calendar, mailbox permissions, or recurring event conflicts → Confirm link is active, import/export is enabled, and calendar owner email matches Hubhus user email.