Early announcements

This page provides an early preview of the key updates, new features, and important changes before they go live. Stay tuned for the latest details and be prepared for what’s ahead.

July 31, 2025 - diligentoneplatform.com to operate alongside highbond.com

On July 31, 2025, Diligent One Platform is releasing the diligentoneplatform.com URL to run in parallel with highbond.com. This is referred to as the dual domain support.

We encourage you to transition to diligentoneplatform.com at your earliest convenience and in alignment with your testing cycles, as all notification links will redirect to the new domain after July 31, 2025.

Impacts of the dual domain transition:

• SSO configuration Organizations using Single Sign-on (SSO) must add an additional identity provider (IdP) to support the new domain.

• Notification emails Notification email domains will change to reflect the new domain.

• SCIM integration Organizations using System for Cross-domain Identity Management (SCIM) must configure a new endpoint URL incorporating diligentoneplatform.com.

The following sections provide further details on each of these impacts.

Include new domain in allow list

If your IT team has allow-listed highbond.com, ensure that they also add the new domain before July 31, 2025.

Single Sign-on

Organizations that have configured SSO with accounts.highbond.com should take action to ensure continuity. To avoid disruption, we recommend that System Admins add an additional SSO Identity Provider (IdP) using diligentoneplatform.com and validate the integration as soon as possible.

To add an additional IdP and validate the integration, follow these steps:

1. Set up a new configuration in your IdP with the following service provider URLs for the Launchpad:

   • Service provider entity ID https://accounts.diligentoneplatform.com/saml/metadata/your_custom_domain

   • Service provider assertion consumer URL https://accounts.diligentoneplatform.com/saml/sso/consume/your_custom_domain

   Important

   To prevent any disruption to your existing configuration, we recommend setting up this as an additional diligentoneplatform.com service provider in your IdP, rather than modifying the current highbond.com setup.

2. Configure an additional SSO provider using the parameters from your newly-added IdP configuration.

   Note

   • Setting up this SSO provider requires public certificates as input rather than certificate fingerprints.

   • If you are an Analytics customer, you can't set up a new provider as public certificates are not supported. You must use the Diligent One token activation to activate an new copy of AN. For more information, see Activate Analytics. For any questions or concerns, contact Diligent Support.

3. Use the following URL to sign in to Diligent One Platform and bypass the custom domain:

   https://accounts.diligentoneplatform.com/saml/sso?custom_domain=your-custom-domain

Notification emails

The dual domain support impacts the notification emails in the following manner:

• With this release, the default sender address for Diligent One Platform notification emails changes from notifications@highbond.com to notifications@diligentoneplatform.com, regardless of the domain used to access the platform.

• To ensure uninterrupted email delivery, we recommend working with your IT team to review and allowlist notifications@diligentoneplatform.com.

• Starting July 31, 2025, links in emails will exclusively point to the diligentoneplatform.com domain.

• Links in emails sent before July 31, 2025, will continue to work as normal.

• Consider informing end users who receive task notifications about the change so they recognize the new domain as a trusted source.

SCIM integration

This update does not require immediate action and can be aligned with your next SCIM token refresh, especially if your current token is nearing expiration. For more information about SCIM token rotation, see Configuring external user provisioning.

Important note for AWS GovCloud customers

• This release does not apply to environments hosted in AWS GovCloud. Support for GovCloud regions will follow later in 2025.

• When released, GovCloud customers will have the one-year migration timeline, starting from the date of that specific release.

For any questions or concerns, contact your dedicated Diligent representative or visit our support page.

March 05, 2025 - GovCloud updates

From March 05, 2025, Diligent HighBond is getting renamed to Diligent One Platform in GovCloud regions (Government Cloud).

The key changes include the following:

• Your working GovCloud environment will now display an explicit FedRamp label to differentiate it from a training system.

• Launchpad has a new look and feel with a consistent, easy-to-navigate experience.

  • The home page displays the apps based on the Diligent products that you have purchased.

  • Apps are categorized for easy navigation, featuring a streamlined look with uniform app icons and a consistent platform experience. For more information about the Launchpad layout, see Launchpad layout.

  • You can use the Customize page option to personalize the home page. For more information, see Customize the home page.

  • ACL Analytics users can access downloads using the Installers tile in the Resources section on the home page.

  • The left navigation menu provides direct links to help documentation, Diligent Support, and Diligent Connect (formerly Community).

The rebrand doesn't change the following:

• The HighBond URL (www.highbond.com).

• The notification email domain (notifications@highbond.com).