Email Integration Data and Permissions

When integrating your GRIN account with Gmail or Microsoft Outlook, you allow GRIN to have certain access and permissions to your email provider. These permissions do not grant GRIN full access to your email inbox. Instead, GRIN only has permission to do the following:

• Compose, attach files to, and send emails in your provider if you do the same in your GRIN Inbox
• Read your provider’s emails’ subject lines, previews, full emails, and threads (including attachments) only if the sender’s email address matches one of your saved creators’ email address in GRIN
• Store your provider’s emails’ subject lines and previews
• Store full emails only if the email was originally composed in your GRIN Inbox
• Read your provider’s folders and labels
• Move your provider’s emails in and out of folders and labels only if you move the corresponding email in your GRIN Inbox
• Star or unstar a message or thread in your provider only if you do the same in your GRIN Inbox and the email is from a creator
• Be notified of new emails to sync to your GRIN Inbox only if the sender’s email address matches one of your saved creators’ email address in GRIN
• If you’ve integrated with Gmail, store and track if an email has been opened, read, or clicked

Provider Scopes

GRIN uses specific authorization scopes, or permissions, from Gmail and Microsoft Outlook which grant the accesses described above. These scopes per provider can be found below:

Gmail:

• gmail.compose
• gmail.modify
• gmail.send
• gmail.readonly
• gmail.metadata

Microsoft Outlook:

• Azure Active Directory Graph:
  • User.Read
• Microsoft Graph:
  • Contacts.Read
  • Contacts.ReadWrite
  • Mail.Read
  • Mail.ReadWrite
  • Mail.Send
  • offline_access
  • openid
  • profile
  • User.Read
• Office 365 Exchange Online:
  • EAS.AccessAsUser.All
  • EWS.AccessAsUser.All

For more information on these scopes, see Google’s Gmail Auth Scopes documentation or Microsoft’s Scopes, Permissions, and Consent documentation.