Skip to content

Products

Compliance Officer Service Expert-led compliance, end to end Compliance Portal Share security documents securely Open-source platform Deploy Probo on your own infrastructure

Resources

Probo stories How teams get compliant with Probo Blog Ideas and guidance from the Probo team Guides & tools Practical compliance guides and free tools Love from Customers What customers say about working with Probo Changelog Latest product updates Download Get the Probo Agent

Company

About The people and vision powering Probo Careers Join the team building Probo Brand assets Official logos and visual resources Security Review our security and compliance posture
Overview Understand Probo and its core concepts Product Explore Probo's GRC capabilities Developers Explore GraphQL, CLI, MCP, n8n, and webhooks Deployment Probo Cloud, self-hosting, and configuration

Explore

GitHub Explore our open-source compliance tools

SendGrid

Connect SendGrid as an access review source using an API key with Teammates access so Probo can list the account owner and teammates.

View as Markdown

Probo reads your SendGrid account’s teammates through the SendGrid v3 API so you can review who has access.

  • Probo organization administrator access
  • SendGrid account owner or administrator access (an administrator holds every scope, including the Teammates permission the key needs)
Probo fieldSendGrid fieldNotes
Namefirst_name, last_nameJoined into a single name, and left empty when SendGrid holds neither
Emailemail
Roleuser_typeowner becomes Owner, admin becomes Admin, teammate becomes Teammate. When SendGrid returns no user_type, the role falls back to Admin or Teammate according to is_admin. Any other value is passed through as is
Adminis_adminFlagged as an administrator when is_admin is true
StatusNot supported
MFAscopesRead from the per-teammate detail endpoint. 2fa_required on its own reports MFA enabled and 2fa_exempt on its own reports it disabled. Both flags together, neither flag, or a failed detail fetch report unknown
Last loginNot supported
External IDusernameStable identifier used to track the account across reviews. On a unified teammate it is the email address
Created atNot supported

The account owner appears alongside the teammates. Probo skips any row that carries no email address.

  1. In the SendGrid app, signed in as the account owner or an administrator, go to Settings > API Keys.
  2. Click Create API Key, name it (e.g. Probo Access Review), and select Full Access, or Custom Access with the Teammates permission set to Read Access.
  3. Click Create & View, copy the key (SG.…), and store it securely. SendGrid shows it only once and cannot retrieve it later.
  1. In Probo, go to Access Review > Connections.
  2. Find SendGrid, click API Key, paste the key, and click Connect.

Probo names the source after the company name on your SendGrid account profile and pulls its teammates into your campaigns.

  • Key rejected. Confirm the key has Full Access, or Custom Access including the Teammates permission. A Billing Access key reaches only billing endpoints. If you did not copy the key value when you created it, you cannot recover it, so create a new key instead.
  • No teammates appear. The key needs at least Read Access to Teammates. A short list can also be correct: Free and Essentials accounts allow one teammate per account, while Pro and higher allow up to 1,000.
  • MFA is unknown for the account owner. SendGrid reports two-factor state through the auto-set 2fa_exempt and 2fa_required scopes. A full-access user, including the owner, holds every scope and therefore both flags, so Probo reports unknown.
  • The source keeps its default name. The name comes from the company field on your SendGrid account profile. Probo keeps the default name when that field is blank, and when the key cannot read the profile. To have Probo pick the name up, fill in the company field and give the key read access to the account profile, or use a Full Access key.