- The addition of new user whitelist rules.
- The descriptions of existing user whitelist rules to be edited.
- Existing user whitelist rules to be removed.

Adding new user whitelist rules
To add new user whitelist rules to your organisation on the Covata Platform:- Ensure you are signed in to Organisation Administration.
- Click the User whitelist option on the left of the Organisation Administration interface to open the User whitelist page.
- Click the Add New button.
-
In the Add Domains/Email Addresses dialog box, click the Add Rule button:
-
Specify a domain or email address under Rule. For example, specify
xy-company.comto whitelist the domainxy-company.comonly.
Notes:-
When specifying a domain, the ‘
*’ wildcard character can be used to include variants of a domain. For example, specify:*.xy-company.comto whitelist domainsqa.xy-company.com,abc.xy-company.com, etc. (but notxy-company.com).*xy-company.comto whitelist domainsxy-company.com,qa-xy-company.com,abc-xy-company.com, etc.xy-company.*to whitelist domainsxy-company.com,xy-company.net,xy-company.abc, etc.
-
When specifying an email address, it is not possible to use the wildcard ‘
*’ character. If the ‘@’ character is present in a rule, then an explicit email address is expected for the rule to be valid, for exampleorg.administrator@xy-company.com.
-
When specifying a domain, the ‘
- ( Optional ) Click under Description (or press the ‘Tab’ key) to specify a description for the user whitelist rule.
-
Repeat the start of step 4 to specify more rules.
Note: If your organisation has many user accounts, be sure to add as many rules as are necessary to prevent this feature denying any unintended Covata users the ability to be shared items as a result of enabling this feature.
-
Specify a domain or email address under Rule. For example, specify
-
Click the Next button to validate the user whitelist rule/s specified above:
- If the rule/s validate/s successfully, the Add Domains/Email Addresses dialog box indicates the email addresses of the Covata users that will be disabled by proceeding.
-
If a validation error message is shown, click the Go Back button and either:
- Click in the erroneous rule’s field (under Rule) to edit + correct its value.
- Click the erroneous rule’s Delete link to remove the rule.
-
Click the Apply button to add the user whitelist rule(s) to the User whitelist page.
Within your organisation, the accounts of Covata users whose email addresses do not match/comply with these user whitelist rule/s above (including any existing rules on the User Whitelist page) are denied the ability to be shared items by any other Covata users. This also applies to any people who do not yet have a user account registered on the Covata Platform.
Editing an existing user whitelist rule’s description
Only the Description of an existing user whitelist rule can be edited. To edit the description of an existing user whitelist rule in your organisation:- Ensure you are signed in to Organisation Administration.
- Click the User whitelist option on the left of the Organisation Administration interface to open the User whitelist page.
- Locate/scroll to the relevant user whitelist rule and click its Edit link.
- In the Edit Description dialog box, modify the rule’s Description as required.
- Click the Save link to save the modifications (or Cancel to discard them).
Removing an existing user whitelist rule
To remove an existing user whitelist rule from your organisation:- Ensure you are signed in to Organisation Administration.
- Click the User Whitelist option on the left of the Organisation Administration interface to open the User Whitelist page.
- Locate/scroll to the relevant user whitelist rule and select its check box on the left.
- Click the Remove button. The Delete Domain/Email confirmation message appears, indicating the Covata user accounts that will be affected by the removal of this user whitelist rule; click Delete to confirm the removal of this rule.
Note: Removing either the last user whitelist rule or all user whitelist rules disables the user whitelist feature. See the note above for more information.

