Supported domains FAQ

Get answers to some of the frequently asked questions on the Diligent One Platform supported domains.

1. What is dual domain?

Starting July 31, 2025, the Diligent One Platform will be accessible through a new URL:

www.diligentoneplatform.com

To support a smooth transition, the platform will also continue to be available at the current URL:

www.highbond.com

This period of dual domain support ensures that both URLs remain functional and secure.

Key dates:

  • July 31, 2025 – Dual domain support begins.

  • July 31, 2026 – Support for highbond.com ends.

2. Are there any exceptions to dual domain support?

Yes, the exceptions are as follows:

  • Products that reach end of life in 2025 support only highbond.com.

  • Products that go live after July 31, 2025 support only diligentoneplatform.com.

To minimize disruption, redirections between the two domains are implemented.

3. How long will highbond.com be supported?

The highbond.com URL will be supported for a year till July 31, 2026.

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. No further action is needed if you have already updated your configuration as described in the next question and answer.

4. What is the impact to HighBond notifications for existing customers?

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.

5. What is the impact to HighBond Single Sign-on (SSO) for existing customers?

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 IDhttps://accounts.diligentoneplatform.com/saml/metadata/your_custom_domain

    • Service provider assertion consumer URLhttps://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

6. What is the impact of dual domain to automated user provisioning (SCIM)?

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.

7. Does the dual domain support impact ACL Analytics or Robotics customers?

The dual-domain rollout will have no impact on ACL Analytics customers, whether they use the desktop client or server agent to publish to the platform. We continue to support and redirect customers publishing to the legacy aclgrc URL, which was in place before the rebranding from Galvanize to HighBond.

While the new URL does not impact analytics functionality, customers currently publishing to legacy URLs will be gradually transitioned to the new domain by 2026. This change will be managed to ensure a smooth experience with minimal disruption.

8. How does the dual domain impact customers on AWS Govcloud environments?

  • 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.

9. What is the main domain users see when they log in to Diligent One Platform?

The domain displayed during a session depends on how users access the platform.

  • If users access the platform using a bookmark to highbond.com, that domain will remain visible throughout their session.

  • If they access it using a link in a notification email sent after July 31, 2025, the domain displayed will be diligentoneplatform.com for the duration of the session.

10. Do bookmarks to highbond.com need to be updated?

Yes, please update your bookmarks from highbond.com to diligentoneplatform.com before July 31, 2026, to ensure continued access to the platform.

11. Will my data change? Will a new version of my environment be set up?

No, your data remains the same and stays in the same environment. The only change is the domain you use to access the platform.