Early access. This feature is in early access, which means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve outputs. Contact the C1 Support team if you’d like to try it out or share feedback.
no-reply@conductorone.com. With a custom email provider, you can send those same notifications from an address on your own domain (for example, governance@yourcompany.com), so recipients see a familiar sender and your email authentication records govern deliverability.
Configuring a custom email provider requires the Super Admin role in C1, plus administrative access to the email service you choose.
Supported providers
| Provider | What C1 uses |
|---|
| Google Workspace | Gmail API with a GCP service account and domain-wide delegation |
| AWS SES | IAM role assumption with an External ID — no access keys shared with C1 |
| Microsoft 365 | Microsoft Graph sendMail API with an Entra ID app registration |
| SendGrid | SendGrid API with a scoped API key |
DNS records
Regardless of which provider you choose, emails sent from your domain will land in spam unless the domain publishes SPF, DKIM, and DMARC records. Configure these records following your provider’s recommended settings — each provider guide links to their authentication documentation.
What happens after you save
When you save a custom email provider configuration, C1 validates the credentials immediately. If validation fails, your previous configuration is preserved and C1 continues sending from no-reply@conductorone.com until the issue is resolved.
To switch back to the default sender at any time, navigate to Settings > Email provider, click Edit, and select ConductorOne-provided.
Test your configuration
After saving, use the Send test button on the Email provider page to send a verification message to yourself. Check the raw headers to confirm SPF, DKIM, and DMARC all pass before relying on the new configuration in production.
