Skip to main content

Overview

Account Domain Controls let you claim ownership of an email domain like example.com and require every log-in and sign-up from that domain to use your account. Use them to make sure everyone at your organization works in a single ngrok account that you’ve set up with the right security controls. You can only create an Account Domain Control on an account that has a single sign-on (SSO) identity provider (IdP) configured.

Availability

Domain Controls aren’t self-serve. To enable them, contact ngrok and the team will help with setup, verification, and pricing.

Verification

To create an Account Domain Control, you must verify that you own the domain. When the Customer Success team creates your Account Domain Control, they ask you to prove that you own the domain. There are several verification methods, but the most common is to create a DNS TXT record on the domain.

Behavior changes

Log in

When an Account Domain Control for example.com exists, anyone who logs in with an example.com email address must use the SSO IdPs configured on your account. The log-in page shows them links to those IdPs.

Account sign-up

When an Account Domain Control for example.com exists, you can block new account sign-ups from example.com email addresses. Instead, those users are redirected to log in with the SSO IdPs configured on your account.

Account creation

When an Account Domain Control for example.com exists, you can prevent ngrok users with example.com email addresses from creating new ngrok accounts.

Email address changes

Users with an email address that matches your Account Domain Control can’t change it to an address outside your domain.

Retroactive account consolidation

Creating an Account Domain Control doesn’t consolidate accounts that users with matching email addresses already created. If you need account consolidation as part of your Account Domain Control, contact Support for pricing.

Pricing

Account Domain Controls pricing is customized to your organization.