Path: Manage Workspace >> Security >> Access Restriction >> Email Based Access Control
Path: Community Settings >> Security >> Access Restriction >> Email Based Access Control
This section is available under Workspace and Community level. It allows to set restriction on the users who join the workspace and community based on their email domain. The administrator of the workspace and the community can auto approve as well as blocklist the email domains.
Email Based Access Control Settings
-
Blocklist: Enter the email domains in this section whose access to the workspace or community need to be restricted.
-
Auto Approve: Enter the domains that have to be auto-approved. The domains should be separated by commas. E.g. @hotmail.com , @mailinator.com, @rediffmail.com.
Any member registering with a domain that is auto-approved in the workspace or community will receive a verification email with a code to verify themselves.
Clicking on the verify my email link will ask you to enter the code in the email and set your workspace or community profile.
-
Invite Members: Enabling this switch will allow the members of the workspace to invite members to join the workspace.
The member will be able to see the invite feature option in the profile dropdown.
You can invite members to join your workspace by selecting the whitelisted domain in the dropdown and invite five members at a time.
4. Allowlist "Invite members" feature to certain domains: The administrator of the workspace can create an allowlist for which users can be invited to the workspace based on certain domains.
5. When Auto Approve list do not match: Select an action to be taken when the email domains mentioned in auto approve list do not match.
a. Moderate Access: Selecting this will put the user with the email address other than auto approved list, in a moderation queue. The moderator of the community will then have to approve or reject the user.
b. Reject Access: Selecting 'Reject access' will display an access prohibition message to the user who is trying to register with a non-approved email address. For example, if @mailinator.com has been blocklisted, it will receive the message as shown in the image below.
6. Update Existing Members as Pending : If Moderate Access is selected under When Auto Approve list do not match dropdown, this option will appear. Setting up Blocklist and Auto Approve list is only applicable to the new registering members. The existing ones will still have access to the community regardless of their email domain. This setting updates the existing members as well and based on their email domain allows access to the community if the email domain matches the approved one. But if it does not match, the members will be put under moderator approval and will not have access to the community till the moderator approves them.
7. Update existing members as Banned: If Reject Access is selected under When Auto Approve list do not match dropdown, this option will appear. Setting up Blocklist and Auto Approve list is only applicable to the new registering members. The existing ones will still have access to the community regardless of their email domain. This setting updates the existing members as well and based on their email domain allows access to the community if the email domain matches the approved one. But if it does not match, the members will be banned from the community.
Access based on Specific or Multiple top level domains
An administrator can limit access based on top level domains. For instance, a university administrator may wish to limit registration to the users based on email addresses at the TLD of .edu.
When IdeaScale worked with the White House on The President's SAVE Awards, the registration was limited to the users with email addresses at government TLDs such as .gov, .mil etc.