Use Your Company Domain To Share Confluence Content Externally

External Share Custom Domain Header Image

We’d all rather share content under our own domain than a third party’s. Why? Because we want the person receiving the information to trust it. They’re more likely to if they know it’s coming from us.

Everybody in the Atlassian community has been hankering after custom domains for Confluence knowledge bases for a looooong time. It’s difficult to offer continuity of services – not to mention confusing and disorienting for the customer – when you’re directing them to a domain that’s not your company’s in order to view your resources. We, too, are stuck with for our public documentation instead of something that’s fully branded to us.

This highly entertaining Jira ticket is a good illustration of the despair, anger, and disbelief that saddles the community over the lack of custom domains for Confluence, Jira, Bitbucket and all other Atlassian Cloud products. It’s the most voted-for Atlassian Cloud backlog issue ever and has just passed its 10th anniversary, with Atlassian still serving up excuses and cop-outs for why this simple feature eludes them.

One user even launched a range of merchandise based on the CLOUD-6999 ticket, including t-shirts, mugs, cushions, clocks, and face masks. The range strapline is: You too can be part of the most epic fail in cloud history by a multi-billion dollar company!

And while it’s not quite within our power to save the day and provide everybody with custom domains for their entire Confluence knowledge base, our new feature can help you retain that continuity of service and brand if all you’re doing is sharing a single page or page tree at a time.

Basically, you can now set up a custom domain for all the Confluence pages you share externally using External Share for Confluence.

Setting up custom domains for sharing content usually comes at a price. However, because we understand the pain of not having custom domains for Confluence (being sufferers ourselves), we’re simply including it in the cost of running External Share.

We think it’s one of those things that’s going to cause people to forget that External Share worked any other way. (Just like when – if – Atlassian finally pulls its fingers out and gives us all custom domains for our cloud apps.)

Let’s walk through it.

By default, all External Share for Confluence links reside under the following domain: If you’d like to share links under a non-External Share for Confluence domain such as then you’ll need to go through the following steps to configure a custom domain. You’ll need to get whoever owns or manages your company domain to do this before you can make shares available from the company website.

Step 1

Configure your Domain Name System (DNS) provider to point to the External Share for Confluence domain: This will usually involve adding a new CNAME record. Consult your DNS provider’s documentation for specific instructions on how to do this. (Please note that there may be a delay in propagating DNS changes.)

Step 2

Go into the Global Settings page of your External Share for Confluence app to set your custom domain. The domain should contain more than 5 letters and/or numbers, and at least 2 dots. It should also start and end with a letter, e.g.

Screenshot of Global Settings in External Share for Confluence

Step 3

Save your domain. Any External Share links created by users on your Confluence instance will now include your custom domain. Change or remove the custom domain simply by clicking “Change”.

Screenshot showing how to change the custom domain

It’s as easy as that! Note that this feature is only available in the Pro version of External Share for Confluence.

If you have any questions or comments about this feature, please do get in touch.

Christopher is a self-confessed nerd who’d probably take the cake on Mastermind if Star Trek: Voyager was his specialist subject. He writes fiction about time travel, conspiracies and aliens; loves roller coasters, hiking and Christmas; and hates carpet, rom-coms and anything with chilli in it. He’s written extensively for technology companies and Atlassian partners and specializes in translating complicated technical concepts, specs and jargon into readable, benefits-driven copy that casual readers will understand.