Integrations at a glance
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.
Each integration page lists the exact permission strings so you can match them against the consent screen your admins will see.