Product | Gem email permissions |
Expert(s) | Enterprise team |
Slack channel | |
This article was last verified on | 06/03/2024 |
🔍 Articles in This Section
Please use the following list to see additional internal articles regarding Gem Access Types & Permissions:
- (Internal) Gem email permissions: Overview
- (Internal) Gem <> Microsoft Graph API permissions
- (Internal) Setting and updating a team's domain mail agent
- (Internal) Process for setting up teams using an on-premise exchange server: Nylas (📍you are here)
While Gmail and Microsoft Outlook (Office 365) are the most common email service providers that we support, and thus why our public documentation refers to them the most, they are not the only email service providers we support. We do support Exchange/Outlook email servers.
That said, the Gem + on-premise Exchange/Outlook integration does require some additional work and customization to be done by our engineering team, to ensure Gem works properly with the customer’s unique setup.
To login to Gem, the customer needs one of the following:
- MicrosoftOnline
- SAML
This is a requirement to get onto the platform. In the past, we’ve sometimes seen customers that use Exchange On Premise set up Microsoft Online accounts to be able to login to Gem. At this time, we cannot support any logins that aren’t Microsoft/Google OAuth or SAML setups.
Once the customer is logged in, we will be able to help get them set up for Email Sending from Gem. Note that Exchange ActiveSync (EAS) must be enabled if they did not login via MicrosoftOnline.
Finally, if they are not able to get past the second login screen, they might need you to share their EAS Server Host name with us directly so that our engineering team can manually configure.
Examples (removing this before repository goes live):