• Products
  • Documentation
  • Resources

Can I change the URL used to access a product?

There are a number of reasons why you may want to change the URL used to access Atlassian products. To make it easier for your team to identify which product instance to use for particular tasks, as a result of a merger or acquisition, or you may want to fully brand your product with your company’s domain.

There are two ways you can change the URL used to access a product:

  • Change the product URL subdomain.

  • Create a custom domain (beta).

Change the product URL subdomain

This is the simplest option. The subdomain is the part of the URL before atlassian.net.

For example, if Acme Corp was acquired by Springfield Limited, you could change the subdomain to reflect the new company name.

acme.atlassian.net is changed to acme-support.atlassian.net

To change the product URL subdomain you must be an organization admin.


There are some limitations to be aware of:

  • You can’t change to a URL that is already in use or was used previously. Because we redirect the old URL, it won’t be available for another site. You’ll need to choose a new, unique URL.

  • You can’t change a product URL more than 3 times.

  • The change applies to all products in that site. You can’t change the URL for individual products within the same site.

In the example below, you can’t change the product URL for acme-partners because that site has been changed too many times. You can change the product URL for acme-support because it has not been changed previously. The change would apply to both Jira and Confluence.

Screenshot showing a free plan you can't update, and a site with higher plans where you can update the product url

Learn how to change the Product URL

Use a custom domain

This feature is currently only available through our Early Access Program.

If you’re not participating in the program you can still change the subdomain of your product URL. Learn how to change a product URL subdomain

If you want to fully brand your product, you can use a domain your company owns. For example, Acme Corp could access their products from the acme.com domain.

acme.atlassian.net is changed to internal.support.acme.com

To add a custom domain you must:

  • be an organization admin

  • be able to add records to your DNS provider

  • have a paid plan for the product you want to change.


There are some limitations you need to be aware of:

  • The feature is in beta, and may not be available to your organization yet.

  • You can only add a custom domain for the Jira Service Management help center at this stage.

  • Apps and integrations that impact the help center may be affected by the change.

  • The fully qualified domain name must be unique. It can’t be already in use and must be public-facing.

  • While you can use your own domain, the fully qualified domain name will need to conform to the following pattern <subdomain>.<subdomainkeyword>.<domain>.

Learn how to add a custom domain

Which approach is right for you?

We’ve summarised the main differences in the table below, to help you decide.

Product URL

Custom domain



Compatible with all apps and integrations.

May not work with all apps or integrations yet.

Can be changed by the Organization admin.

Can be requested by the Organization admin.

Does not require you to make any manual DNS changes.

Requires you to add several records to your DNS to confirm ownership.

You can only change the subdomain, you can’t change atlassian.net domain.

You can use your own domain, but your fully qualified domain name needs to conform to a specific pattern.

Can only be changed a maximum of 3 times, and you can’t reuse previous URLs.

No limit to the number of changes, or to reusing previous fully qualified domain names.

Generally available for Confluence, Jira Software, Jira Service Management in any organization.

Beta functionally. Only available for Jira Service Management help center.

Quick to set up, and the new URL is available to use almost immediately.

Takes some time to set up, and for the DNS to propagate.


Additional Help