Skip to main content
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

All browser traffic to Exec flows over TCP port 443. Allow the firewall domains listed above through your corporate firewall.

​
Voice Roleplay Audio Quality

Voice roleplays work with only the TCP 443 entries above. For the best audio quality, also allow the outbound UDP rules below so calls can take a direct media path instead of relaying over TLS. These UDP rules are optional. When they are blocked, calls automatically fall back to *.turn.livekit.cloud over TCP 443.

​
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.