Set up a Twilio SendGrid connector

C1 provides identity governance and just-in-time provisioning for Twilio SendGrid. Integrate your SendGrid instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Scopes
Subusers
Teammates
Teammate invitations

Additional functionality:

Supports automatic account provisioning and deprovisioning

New teammates are invited by email with optional scopes and admin permissions:

• is_admin: Whether the teammate has admin privileges (default: false).
• scopes: List of permission scopes for non-admin teammates (default: “user.profile.read”). Scopes are ignored when is_admin is true, as admins have full access.

Gather SendGrid credentials

Configuring the connector requires you to pass in credentials generated in SendGrid. Gather these credentials before you move on.

Create a SendGrid API key

1. In SendGrid, navigate to Settings > API Keys.

2. Click Create API Key.

3. Give your API key a name, such as “C1 integration”.

4. Select Full Access.

5. Click Create & View.

6. The new API key is created. Carefully copy and save the API key.

Done. Next, move on to the connector configuration instructions.

Configure the SendGrid connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of SendGrid credentials generated by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for SendGrid and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. Find the Settings area of the page and click Edit.

8. Enter the required configuration:

   • sendgrid-api-key (required): API key for SendGrid service.
   • sendgrid-region: Region for SendGrid service: global or eu. (default: global)
   • ignore-subusers: Ignore subusers in the SendGrid account, subusers are an upgraded feature of sendgrid.
9. Click Save.

10. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your SendGrid connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the SendGrid connector connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new SendGrid connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your SendGrid connector deployment:

Secrets configuration

# baton-sendgrid-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sendgrid-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # SendGrid-specific credentials
  BATON_SENDGRID_API_KEY: <SendGrid API key>
  BATON_SENDGRID_REGION: <SendGrid service region (defaults to global)>

  # Optional: include if you want to skip syncing SendGrid subusers
  BATON_IGNORE_SUBUSERS: <true>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-sendgrid.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-sendgrid
  labels:
    app: baton-sendgrid
spec:
  selector:
    matchLabels:
      app: baton-sendgrid
  template:
    metadata:
      labels:
        app: baton-sendgrid
        baton: true
        baton-app: sendgrid
    spec:
      containers:
      - name: baton-sendgrid
        image: public.ecr.aws/conductorone/baton-sendgrid:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-sendgrid
        envFrom:
        - secretRef:
            name: baton-sendgrid-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the SendGrid connector to. SendGrid data should be found on the Entitlements and Accounts tabs.

Done. Your SendGrid connector is now pulling access data into C1.