Domain ownership for SSO (single sign-on)

Subscription administrators must claim and verify ownership over one or more domains before they can manage the SSO settings for users in their subscription. Once a subscription administrator has verified ownership of a domain, they will be able to manage the SSO settings for users that have a user name that uses this domain. 

For information on how to verify a domain, see the Setting up SSO article.

For example

A user with the user name greg@mydomain.com is a subscription administrator in Span Workspace. The subscription administrator invites the following users from his company to the subscription:

tony@mydomain.com

elayna@mydomain.com

riley@mydomain.com

The subscription administrator also invites the following additional users to this subscription. These users have user names that have a different domain:

mathew@otherdomain.com

alison@otherdomain.com

At this point in time, as the subscription administrator has not claimed and verified ownership over any domain, they will not be able to manage the SSO settings for any of the above users.

If the subscription admin now follows the process to claim ownership over the ‘mydomain.com’ domain when this process is completed successfully they will be able to manage the SSO settings for the users matching this domain. That is

tony@mydomain.com

elayna@mydomain.com

riley@mydomain.com

Other users in the subscription will not be affected.


Top level domains and sub domains

If you claim and verify ownership of a top level domain you will be able to manage SSO settings for users matching any related sub domain.

In the above example, where the subscription administrator owns the top level domain ‘mydomain.com’ he or she would be able to manage SSO settings for users in any sub domain. For example, ‘subdomain1.mydomain.com’, ‘subdomain2.mydomain.com’ and so on.

If you claim and verify ownership of a sub domain, for example ‘subdomain1.mydomain.com’ you will only be able to manage the SSO settings for users that match the subdomain. In the example of ‘subdomain1.mydomain.com’ you would not be able to manage SSO settings for users in ‘mydomain.com’ or in ‘subdomain2.mydomain.com.’ You can only manage SSO settings for users in ‘subdomain1.mydomain.com’ and any other subdomains under it.


Deleting a domain

If you are no longer the owner of the domain or simply wish to remove it from Span Workspace you can delete it using the three-dot menu beside the domain.

If you delete a domain, the related SSO identity providers linked to user accounts will be removed and will no longer be options for these users to use at login.


Last updated: November 14, 2018

Was this article helpful?

Can’t find what you’re looking for?

Contact Support

1.844.370.2111