Restrict invites by top level domain

[ackernaut]

This customer 🔒 was surprised to find out that users within their account could invite anybody (any email address), and that those users were also able to do the same. In Loom, at some point after 27:14 🔒 , he suggested the idea of being able to restrict this by email domain.

I’m opening this discussion to gather any similar feedback from other customers, and to see if this is something we should explore. Is this a feature? Is it a paid feature?

Related: there is an issue about designing functionality to restrict invites and new sign-ups to SSO/SAML users, see #5512 — is this how we solve for this?

[gcrickman]

This Enterprise customer 🔒 also requested:

I would like to know how can we restrict access to certain domain for our organization? We would like to just have @xxxx.com email addresses.
Also, how can we control new invites? Only org admins can send invite to new people.

[gcrickman]

This customer 🔒 requires restrictions in order to use their private managed instance. Currently, we have implemented IP restrictions to try to solve this but a domain lock would solve this problem.

[avivapinchas]

This is now available as an Enterprise feature!

[ackernaut]

Woo hoo! Are we getting back with folks who asked for this? At any rate I imagine it’ll come up with any forward motion with customers