Email glossary · Practical guide
OAuth: delegated authorization for a connected mailbox
OAuth allows an application to receive delegated authorization through tokens. It does not mean the application has unlimited access or that every mailbox protocol is enabled.
Reviewed · Examples are illustrative
Who this helps: Readers checking a term before making an outreach or mailbox decision.
Meaning and common confusion
The provider, requested permissions, account policy and application implementation determine the usable access. Completing a consent screen is one stage. The app must still obtain and use appropriate tokens, connect to supported services and handle expiration or revocation.
Worked example
This is a synthetic illustration, not a customer result or a live configuration to copy.
User authorizes an app
App receives scoped authorization
Mailbox connection is tested separately
If policy blocks the protocol, consent alone does not override that decision.Checks to make
- Confirm the provider account and application identity before authorizing.
- Review requested access and organization policy.
- Verify a controlled send and incoming reply after connection.
Next step and limits
Use the provider connection guide for the exact supported workflow. Do not paste access or refresh tokens into support chats. Zintara's mailbox connection authorization is separate from signing in to the Zintara application itself.
Source references
Worked examples are illustrative. Editorial procedures are suggested methods, not measured performance claims or promises of additional product features.
Related guides
- OAuth vs app password: choose the supported mailbox connection →
- Refresh token: renew access without treating authorization as permanent →