Integration Scopes

Revenue.io requests specific Microsoft OAuth scopes so users can connect Exchange or Office 365 email and calendar for Meeting Assistant, Guided Selling email, and scheduling pages.

What the integration provides

Revenue.io provides email and calendar integrations for Microsoft Exchange and Office 365 accounts, powered by the Nylas API.

Key capabilities include:

• Meeting Assistant: Allows a user’s Meeting Assistant Bot to automatically join meetings from connected calendars.
• Email integration: Enables users to send emails directly from Microsoft Exchange within Guided Selling.
• Scheduling pages: Allows users to create and manage scheduling pages for easy meeting booking with prospects and customers.

How users connect to Revenue.io

Users must individually grant access to their email and calendar accounts through the Revenue.io integrations page as part of a secure, user-authorized OAuth 2.0 connection. The Nylas API interfaces with Microsoft’s Graph API.

1. Open the Admin Console.
2. Go to User Settings → Integrations.
3. Click Connect under Exchange/Office365.
4. Complete the OAuth sign-in flow on the mail or calendar provider’s website.

For detailed step-by-step instructions, refer to Connect Microsoft Exchange/365 to Revenue.io or the Support Knowledge Base for Exchange.

OAuth scopes

Microsoft scopes

Required scopes:

• User.Read – Read user’s basic profile
• profile – Access to basic profile information
• openid – OpenID Connect authentication
• offline_access – Maintain access to data after initial consent
• Mail.ReadWrite – Read and write access to user’s mailbox
• Mail.Send – Send email as the user
• Calendars.Read – Read user’s calendars
• Calendars.ReadWrite – Read and write access to user’s calendars

Frequently asked questions

Q: Are all scopes required? Are any optional?

A: All listed scopes are required. The platform requests only the minimum permissions necessary for the integration to function properly, and each scope serves a specific purpose:

• Email scopes enable sending emails, reading messages for reply tracking, and managing drafts.
• Calendar scopes enable meeting discovery, scheduling page functionality, and calendar event synchronization.
• Profile and authentication scopes are required by OAuth 2.0 standards for secure user identification.

Removing any scope would block core functionality of the integration. The platform does not request any unnecessary permissions such as shared mailbox access. Scope is restricted to the individual user who is granted access.