This page lets you ‌configure network settings for cloudimanage.com. When configured, these settings are applied across all iManage Work libraries.

Application and tool requirements

Before enabling these features, ensure users are on the minimum required versions of these iManage Work clients:

• iManage Work Desktop for Windows 10.5.1 or later

• iManage DeskSite or FileSite 9.3.7 or later

You should also confirm that all third-party tools in your environment are supported before enabling these features.

About custom subdomains and seamless SSO

Custom subdomains

A custom subdomain is a company-specific name you can apply to the cloudimanage.com URL. After it's configured, your users can access iManage Work using either the cloudimanage.com URL or the URL that includes your subdomain, such as company.cloudimanage.com.

Benefits include

• After a subdomain is configured, you can enable Seamless SSO, which simplifies the sign-in experience for your users.

• A custom subdomain can help with communications with your iManage Work users, and ultimately drive adoption as users sign in to a URL with a familiar name.

Seamless SSO

When a custom subdomain is configured in your environment, you can take advantage of Seamless SSO.

• Users accessing iManage Work from the custom subdomain are automatically directed to your company's SSO provider, without needing to enter their email address in the iManage Work sign-in dialog.

• Users can continue to sign in to the cloudimanage.com URL. In this case, they're first prompted to enter their email address in the iManage Work sign-in dialog, and then are redirected to your company's SSO provider for authentication. After successful authentication, users are automatically redirected to your custom subdomain. 

Configure a custom subdomain and enable seamless SSO

Once a custom subdomain is configured, users signing in to cloudimanage.com are automatically redirected to the custom subdomain URL. Users may also sign in directly using the custom subdomain URL (company.cloudimanage.com).

To configure a custom subdomain:

1. In Control Center, browse to Network & Security > Network Settings.

2. In the Custom Subdomain section of the Network Settings page, select +Add.

3. In the Add Custom Subdomain dialog, select the Help Center: Best Practices for Enabling and Removing a Custom Subdomain (may require login) link.

   1. After you’ve reviewed the Help Center article, select the I have read and understand the risks check box, and then select Next.

      

4. To use a custom subdomain, slide the Use custom subdomain toggle to the right.

   Figure: Add Custom Subdomain dialog

   

5. In Subdomain, enter the text for your custom subdomain.

   • Subdomains must be 2–63 characters.

   • Special characters are not allowed.

   • Dashes (-) are allowed, but can't be used as the first or last character.

   • Uppercase characters aren't allowed. If you enter an uppercase character, it's automatically converted to lowercase.

   • Subdomains must be globally unique. You'll receive a message notifying you if the subdomain you entered is already registered.

6. To enable seamless sign-in, slide the Seamless Sign-in toggle to the right. This allows Enterprise users to be immediately directed to their Identity Provider (IdP) for authentication without first needing to enter their email address on the iManage Work sign-in screen.

7. Select Save.

The new subdomain may take up to four hours to become active. Contact iManage Cloud Support if you require modification or removal of your custom subdomain.

About OAuth Token Absolute Timeout

OAuth Token Absolute Timeout sets the maximum lifetime for access tokens, regardless of user activity. This setting prevents authentication tokens from remaining valid indefinitely through continuous active use.

Idle timeout versus Absolute timeout

• Idle timeout (Access Token Expiry): Revokes tokens only after a user is inactive for a defined period. If the user remains active, the session stays alive. Configured per application.

• Refresh Token Expiry: Controls how long a refresh token can be used to obtain a new access token without the user needing to sign in again. This setting determines how long an application can keep a session live through normal refresh activity.

• Absolute timeout: Imposes a maximum access token lifespan from the moment of authentication. When the configured duration is reached, the access token is revoked even if the user is actively working. However, if the application has a valid refresh token, it can still obtain a new access token without requiring the user to sign in again. Configured once, organization-wide.

Table: Comparison of Idle timeout and Absolute timeout

Interaction with existing token settings

The existing Access Token Expiry and Refresh Token Expiry settings continue to apply. OAuth Token Absolute Timeout doesn't replace these settings—it works with them as an additional hard limit. Tokens are revoked when the first applicable expiration condition is met.

When the Absolute timeout is reached, the access token is revoked. If the application has a valid refresh token—and the Refresh Token Expiry limit hasn’t also been reached—it can use that refresh token to obtain a new access token without requiring the user to sign in again.

Configure OAuth Token Absolute Timeout

Administrators can configure the Absolute timeout duration from the Network Settings page in iManage Control Center.

1. In iManage Control Center, browse to Network & Security > Network Settings.

2. In the OAuth Token Absolute Timeout section, select Edit.

   Figure: OAuth Token Absolute Timeout setting

   

3. In the Edit OAuth Token Absolute Timeout dialog, slide the Enable Absolute Timeout toggle to the right.

4. In the Timeout Duration field, enter the desired duration. The equivalent value in seconds is displayed beneath the field.

5. From the time unit drop-down list, select Hours or Days.

6. Select Save.

   Figure: Edit OAuth Token Absolute Timeout dialog