Closed cloudkompute closed 5 years ago
Issue-Label Bot is automatically applying the label feature_request
to this issue, with a confidence of 0.95. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
A super-admin could be probably allowed to maintain the names of the restricted domains.
Good plan! There are quite a few nice NPM packages for this, I'll make sure to add that validation. The feature of email restriction actually doesn't work, it's currently just a setting you can save, but I plan on shipping that this week too.
We already have a helper function for detecting educational emails using my package Edumail, and something similar can be used to prevent free/temporary/disposable email addresses too.
I've added a Staart-wide check for disposable emails while signing up or inviting a member. You can use the environment variable ALLOW_DISPOSABLE_EMAILS
to control the setting. By default, disposable emails are not allowed.
For teams and company domain emails, I will make sure also not allow public email providers like Gmail, that's in the works! 😄
Great!
I'd like to request to create a super-admin role that controls the list of restrictive domains like gmail, etc.
Staart now has support for whitelisted domains:
You can add any number of domains to your team, and verify them by uploading a file or adding a DNS TXT
record:
Then, you can choose to:
Email domain: Enter your company's domain, eg. oswaldlabs.com We'll allow people with emails from this domain to join this organization automatically
Do not allow the public domains to be included in this list like gmail, hotmail, rediffmail, and many others.