Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.exec.com/llms.txt

Use this file to discover all available pages before exploring further.

This guide lists the domains, ports, and email sender addresses that IT and infosec teams need to allow so Exec works on your corporate network and so Exec emails reach your users.

​
Quick Reference

CategoryValuePurpose
Protocol and portTCP 443 (HTTPS / WSS)All browser traffic
Firewall whitelist*.exec.comApp, login, and customer workspace
Firewall whitelist*.execprod.ioSupporting production services
Firewall whitelist*.vapi.aiVoice roleplay API and signaling
Firewall whitelist*.daily.coVoice roleplay media transport
Email sendermg.exec.comTransactional email sender
All browser traffic to Exec flows over TCP port 443. Allow the firewall domains listed above through your corporate firewall.

​
Email Sender Whitelist

Exec sends transactional email (user invitations, password resets, notifications) from mg.exec.com. Your email security gateway or mail transport rules need to allow or trust this sender domain so Exec emails are not quarantined or routed to junk. This is typically handled by the IT or messaging team rather than infosec.

​
SSO and MFA

For customers who want authentication controls beyond named user accounts, Exec supports SSO via SAML and OpenID Connect. MFA is inherited from your identity provider. See Single Sign-On and Directory Sync for setup instructions and supported identity providers.