> ## Documentation Index
> Fetch the complete documentation index at: https://docs.junojourney.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations Toolkit for IT

> Every permission Juno requests across its integrations — why we need it, what data we access, and what we do with it.

This toolkit is written for IT and security teams reviewing Juno. Each page covers one integration and answers three questions: why Juno integrates with the service, which permissions we request, and what we do with the data.

## Integrations at a glance

| Integration                                                                          | Purpose                                                  | Who consents                                        | Auth model                                                        |
| ------------------------------------------------------------------------------------ | -------------------------------------------------------- | --------------------------------------------------- | ----------------------------------------------------------------- |
| [Google Calendar](/integrations-toolkit/google-calendar)                             | Room booking and Juno-managed event invites              | Google Workspace admin                              | Admin OAuth consent + service account with domain-wide delegation |
| [Outlook Calendar](/integrations-toolkit/outlook-calendar)                           | Room booking and event calendar sync                     | Microsoft Entra admin                               | Admin OAuth consent (Microsoft Graph)                             |
| [Zoom](/integrations-toolkit/zoom)                                                   | Create meetings for events, attendance, recordings       | Meeting organizer (per user)                        | OAuth 2.0, Zoom Marketplace app                                   |
| [Microsoft Teams meetings](/integrations-toolkit/microsoft-teams-meetings)           | Create Teams meetings for events, attendance, recordings | Meeting organizer (per user)                        | OAuth 2.0 delegated (Microsoft Graph)                             |
| [Google Meet](/integrations-toolkit/google-meet)                                     | Create Meet links for events, attendance                 | Meeting organizer; optional org-level reports grant | OAuth 2.0; optional service account with domain-wide delegation   |
| [Slack](/integrations-toolkit/slack)                                                 | Deliver Juno notifications in Slack                      | Slack workspace admin                               | Slack app with bot token                                          |
| [Microsoft Teams notifications](/integrations-toolkit/microsoft-teams-notifications) | Deliver Juno notifications in Teams                      | Teams admin (app approval)                          | Bot Framework app                                                 |
| [Email, SMS and push](/integrations-toolkit/email-sms-push)                          | Deliver notifications outside chat tools                 | No org consent needed (Juno-operated)               | Juno-managed provider accounts                                    |

## How Juno handles credentials

These practices apply to every integration in this toolkit:

* **Least privilege** — Juno requests only the scopes each feature needs. Optional features (for example, recording download) use separate, optional scopes.
* **Encryption at rest** — OAuth tokens and API credentials are encrypted before storage and are never exposed to the browser or client apps.
* **No passwords stored** — Juno never sees or stores your users' passwords for any integrated service.
* **Revocable at any time** — every integration can be disconnected from Juno or revoked from the provider's admin console. Each page includes revocation steps.
* **Tenant isolation** — credentials and synced data are scoped to your organization and are never shared across Juno customers.

<Note>
  Each integration page lists the exact permission strings so you can match them against the consent screen your admins will see.
</Note>