Change a realm’s URL – Quickbase Help

Realm admins can change the URL of a realm by submitting a case to Quickbase technical support.

When changing the URL, anything that depends on knowing the address for your Quickbase account should be assessed or reconfigured to ensure it continues to work as expected. When a request is made to a valid app or table ID using an incorrect URL, Quickbase automatically redirects the request to the correct realm and returns an HTTP 301 Permanent Redirect response. However, it's important to still update incorrect realms wherever you find them because:

Scripts may or may not follow the re-direct
Successful redirects may be rate-limited to protect the Quickbase platform

To reduce breakages as much as possible, use a realm alias when making this change.

This article explains actions to take to ensure your apps and pipelines continue to run as expected after the URL change.

In this article

Use a realm alias

A realm alias is a secondary realm URL that points to the same Quickbase realm. When enabled, both the primary and realm alias URLs work for users and integrations. Sessions are shared between both realms, meaning signing in to one URL signs you into the other.

To create a realm alias, request it when submitting a support ticket to change your realm’s URL.

Best practices for using a realm alias

Quickbase recommends you configure your realm as follows:

Set the new realm as the primary URL
Set the original realm as the realm alias

This ensures the new URL name appears across all areas in Quickbase, while the alias acts as a fallback to avoid breaking functionality.

If you want to remove the alias, create a support ticket.

Limitations

Some areas of Quickbase only show or use the primary realm URL. That means that even if you are using the alias URL, the primary realm URL will still be used in some places. This includes:

Login messages
Email notifications
Audit log links
Most admin console pages
App settings and Table settings structure
Formulas that use URLRoot()

Reconfigure apps with the new realm URL

The following table includes all areas to check before changing your realm’s URL.

Area to check	Redirect behavior	Realm alias behavior
Pipelines	Redirects are not supported.	Pipelines work with both the primary realm URL and the realm alias, though exceptions may occur. If you need assistance, realm admins can open a technical support ticket.
Connected tables	Redirects are not supported.	Existing Quickbase or Admin Console connections using the realm alias continue to work, but should be updated to reflect the new realm URL. These connections must also be updated before removing the alias. To do so, go to connection settings from the connections list in your user profile. If the apps in your realm are used as a source for connected tables in another realm, the other realms that are pulling data must: Use the new realm URL in the connection If the connected table is connecting to a realm that has cross-realm security configured, include the connected table’s new realm URL in its list of allowed realms
Actions (retirement announced)	Actions may automatically redirect to the new realm URL, but this functionality is not maintained.	Actions may work with both the primary realm URL and the realm alias, but this functionality is not maintained.
Webhooks (retirement announced)	Webhooks may automatically redirect to the new realm URL, but this functionality is not maintained.	Webhooks work with both the primary realm URL and the realm alias, but this functionality is not maintained.
External scripts	External scripts that call the Quickbase XML API redirect to the new realm URL if they respect HTTP 301 redirects. Scripts that call the REST API will not redirect.	External scripts that call Quickbase from outside sources work with both the primary realm URL and the realm alias.
Code pages	Code pages redirect in most browsers, though exceptions may occur.	Code pages that contain Javascript, HTML, etc. that reference the URL work with both the primary realm URL and the realm alias.
URL formulas	URL formulas containing the `URLRoot()` function use the new realm URL.	Formulas that use `URLRoot()` always use the primary realm URL.
Authentication	N/A	Authentication must match your primary realm URL, which might require configuration in your IDP. Learn more about configuring SAML authentication in Quickbase.
Bookmarks and other saved links	Bookmarks and saved links redirect in most browsers, though exceptions may occur.	Bookmarks and links work with both the primary realm URL and the realm alias.
FastField	Redirects are not supported for the Quickbase integration.	FastField global workflows that use the Quickbase integration continue to run with both the primary realm URL and the realm alias. For connections that use a Quickbase user token in global workflows, you must update the realm’s URL for the integration. For SSO connections to Quickbase, a realm admin must open a technical support ticket to update the realm’s URL.

Important

Features that have reached end of life cannot be recreated using the new realm URL.
Contact technical support for any specific concerns.