Skip to content

Latest commit

 

History

History
41 lines (25 loc) · 2.34 KB

organization-level-custom-domain.md

File metadata and controls

41 lines (25 loc) · 2.34 KB

Organization-level custom domain

{% hint style="info" %} Please follow the steps to set a custom domain in this order:

  1. Choosing a subdomain
  2. Deciding where to set the custom domain
  3. Initiating the custom domain setup (at the organization, collection, or space level) (you are here)
  4. Configuring DNS
  5. Confirming the custom domain setup {% endhint %}

{% hint style="warning" %} Before you’ll be able to set a custom domain for your organization, at least one space owned by the organization will need to be published. If all of the spaces are unpublished, you won’t see the publishing section on the organization settings page. {% endhint %}

You’ll find the options for setting a custom domain for an organization within the organization settings page. Open the settings menu in the lower left corner, and click on [Org Name] Settings.

On the next page, in the Publishing section, under Custom Domain, click Connect a domain.

Set a domain for your entire organization in settings.

This will open up a window where you can enter the custom domain, and then click Next: Configure DNS.

Connect a custom domain

We’ll then provide the name and value to use in the next step when you create your CNAME DNS record. You can copy the name or value to your clipboard by clicking on the icon on the right-hand side of each field.

The name and value for the CNAME record

The value for the CNAME record will be in the format [something]-hosting.gitbook.io, where that [something] will be unique to you. Make sure to use the value displayed to you in the GitBook app, and not the value in the screenshot above! 🙂

Now, you’re ready to move onto the next step: configuring DNS.