SAML For Organizations

The Remote.It Business, Fleet, and Enterprise Plans offer an optional custom integration of SAML-compatible authentication for the Remote.It accounts under a single email domain.  Subscribers have the option to request SAML activation through the Organization Settings page in the Remote.It Desktop or web portal.  With SAML authentication Remote.It users with accounts using the same email domain can use their company sign-in credentials when signing into Remote.It.

This does not give immediate access to the Organization, you must still invite and assign a role for organization members.


Enable SAML in

To be able to enable SAML, you must have access to your DNS settings for your domain.


Once your domain is entered, you will be presented with a custom CNAME host name and VALUE.


The final record in your DNS should look similar to the below record. This record may take 20 minutes to fully populate before you can validate your domain in the app.



Once the DNS records have been validated, you can now move forward with importing the metadata file from your identity provider.


Configuring Single Sign On (SSO) via SAML in your Identity Provider

Contact your IT team to create a new Single Sign On (SSO) application with the following information and provide them with the list of users in your organization who should have access to the application on your side. After configuration has completed, you should have the ability to download a XML metadata file to upload directly into the above page.

Basic SAML Configuration

Unique Identifier (Entity ID/Audience)


Reply URL (Assertion Consumer Service URL/ACS)

Relay State (Optional)

Required Claims

Unique User Identifier/Name ID

email address

Claims (Listed as Optional in the General configuration)

family_name(last name)
given_name(first name)


Sign In

All you or your users need to do is enter the email address on the sign in page and they will be asked to authenticate in your identity provider and be able to access their account. SAML has no impact on their access to organizations or licensing and that will need to be configured in the Organization.




Was this article helpful?
0 out of 0 found this helpful