Send to Coworker action removed from Domain Authentication
Twilio SendGrid removed the Send to Coworker action from Domain Authentication setup due to low usage and security concerns. Users should now share DNS configuration details directly through internal communication channels like Slack or ticketing systems instead of email.
Effective August 3, 2026, Twilio SendGrid has removed the Send to Coworker action from the Domain Authentication setup flow due to low usage. This simplification prioritizes only the most valuable paths for users to complete their domain authentication and get started with email.
Directing DNS records through automated email is no longer the optimal method for technical handoffs. DNS configurations are highly sensitive to formatting, and transferring this data via email can increase the risk of errors during the setup process. This change ensures that critical security records are managed through more intentional and reliable methods.
For users of the Send to Coworker action, Twilio SendGrid recommends reaching out directly to your IT or infrastructure teams via internal communication channels, such as Slack, Microsoft Teams, or internal ticketing systems. Sending DNS record update requests through internal communication channels ensures recipients trust the request. Utilizing these established workflows also delivers the necessary context and data in a format that aligns with an organization’s standard practices for updating DNS records.
Source: original entry ↗
More from Twilio
Follow Twilio to get its new changes in your feed and email digest.
Voice Integrity now supports all three major US networks
Voice Integrity, part of Twilio's Voice Trust offering, now supports all three major US carrier networks. Businesses can register their details and outbound phone numbers directly with carriers to help identify legitimate traffic and reduce spam blocking.
Unified Login for SendGrid Marketplace Customers
SendGrid marketplace customers can now create individual Twilio logins for each user, enabling granular permission management instead of shared admin access. This rollout applies to all marketplace integrations including Azure, Google Cloud, Heroku, and AWS.
Webhook Configuration API is now Generally Available
The Webhook Configuration API enables customers to configure authentication and delivery settings for outbound webhooks on a per-URL basis through Webhook Settings and Webhook Rules resources.