For some of our most security-conscious customers, such as customers in the medical industry who may have Protected Health Information (PHI) in their email, we support requesting more limited email access permissions. Limited access grants Gem access email headers (like the to/from email addresses and timestamp), but not the contents of the emails in your inbox.

By default, Gem requests access to read, send, and delete email from your inbox. You can read more about why Gem requires these permissions here.

Both Gmail and Outlook 365 have APIs that allow Gem to request more limited access to email inboxes. Unfortunately, more limited access is not supported for customers with a legacy Exchange/Outlook email server. 

Limiting Gem's access to email will disable features in Gem. We've attempted to list the ones we know about here, but as we continue to develop the product, new features may come out that your team may not have access to as a part of this decision.

  • More inaccurate open tracking, and inaccurate click tracking While there are some caveats to open tracking even for customers that grant Gem full access to email inboxes, there are more cases that may cause inaccuracies for customers on the limited permission set. Specifically, open counts are normally higher after a candidate replies in the standard integration, but with limited access to email, they can now be inaccurate even before a candidate replies. This is because, since Gem no longer has access to delete mail from inboxes (which we use to work around this issue), we can no longer tell whether the sender has opened the email or the recipient has.
    Similarly, we can no longer tell the difference between the sender clicking on links in the message and the recipient. So if the sender goes into their sent mail and clicks on a link, click counts may now be inaccurate.
  • No reply content when sending from a different email account Normally, when you send as a hiring manager, we notify the sender of the sequence when a candidate replies, along with the content of that candidate's reply. Because Gem can no longer see the contents of messages, your team will have to contact the hiring manager to learn whether that recipient replied positively or negatively.
  • No Greenhouse email content sync to the Greenhouse activity feed For our customers who have enabled our system to sync email content sent outside of Gem to the Greenhouse activity feed, this feature will be disabled. This is because we can no longer see the content of emails.
  • No future features around email content We often get requests to show email content sent outside of Gem in the Gem activity feed for a candidate. When we build this functionality, it will not be supported for limited access customers. Customers will retain our current functionality, which shows who on the team sent or received an email with the candidate outside of Gem, and when.

Did this answer your question?