Skip to main content
OAuth permissions should always be explained in terms of the user-facing value they unlock.

Good permission explanations

ProviderWhy the user is asked
LinkedInTo connect profile and first-degree relationship context
GoogleTo add communication, meeting, and contacts metadata
MicrosoftTo add Outlook communication and calendar metadata

Documentation rules

  • explain what data is used
  • explain what product behavior it unlocks
  • explain what happens if the user disconnects
  • avoid vague “improve your experience” language when a concrete explanation is possible