# Publish a docs site

Once you’ve finished writing, editing, or importing your content, you can publish your work to the web as a docs site. Your docs will be published on the web and available to your selected audience.

The content on your site comes from [spaces](https://gitbook-v2-hxa0n9y0h-gitbook.vercel.app/url/gitbook.com/docs/creating-content/content-structure/space) in your organization. When you create a new docs site, you can create a new space, or link an existing one.

<figure><img src="https://1050631731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2FMHFgq8cFWJlX99QPv02O%2F18_07_25_publishing-documentation-publish-docs.svg?alt=media&#x26;token=832dc431-6ae1-4f14-ae63-0b3b9d98ac99" alt="A GitBook screenshot showing the docs sites homepage"><figcaption><p>GitBook's docs sites homepage.</p></figcaption></figure>

### Create a docs site

To create a docs site, click the plus **+** icon next to Docs site in the sidebar to launch the docs site wizard.

Give your site a name, choose a starting point for your content, and select whether you want to publish your site now or later.

If you already have content in a space that you would like to use, you can create a docs site directly from that space by opening the space and clicking **Share** in the top-right corner of the window. Then choosing **Publish as a docs site** from the share modal.

### Publish a docs site

By default, your site will be published publicly. You can change your site’s visibility in your [site’s settings](https://gitbook-v2-hxa0n9y0h-gitbook.vercel.app/url/gitbook.com/docs/publishing-documentation/site-settings).

There are three primary options to choose from when publishing your site:

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Public</strong></td><td>Publish your docs publicly to the web.</td><td></td><td><a href="https://1050631731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2Fh07YAPTJAFEf2OChagKd%2FPublic.svg?alt=media&#x26;token=0ef630f6-f263-4acb-a3f9-e8c99d88ee96">card_publish_public.svg</a></td><td><a href="publish-a-docs-site/public-publishing">public-publishing</a></td></tr><tr><td><strong>Privately with share links</strong></td><td>Publish your docs with private share links.</td><td></td><td><a href="https://1050631731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2FJiRinaF7WqJ8IBGdU8oE%2FPrivately.svg?alt=media&#x26;token=99376132-1d66-4125-8a18-1ab35e90e385">card_publish_privately.svg</a></td><td><a href="publish-a-docs-site/share-links">share-links</a></td></tr><tr><td><strong>Authenticated Access</strong></td><td>Protect your published docs behind an OAuth sign in.</td><td></td><td><a href="https://1050631731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNkEGS7hzeqa35sMXQZ4X%2Fuploads%2FiSv6u28TbniLRbdoAqJg%2FVisitor%20Authentication.svg?alt=media&#x26;token=5a829cf4-9505-4320-9e80-ca24e5f89c4f">card_publish_visitor_authentication.svg</a></td><td><a href="authenticated-access">authenticated-access</a></td></tr></tbody></table>

### Delete or unpublish a docs site

To delete a docs site, you’ll need to open your site’s dashboard, then open [**Site settings**](https://gitbook-v2-hxa0n9y0h-gitbook.vercel.app/url/gitbook.com/docs/site-settings#delete-site) from the top-right corner.

### Site editing permissions

Docs sites inherit the editing permissions from the [spaces](https://gitbook-v2-hxa0n9y0h-gitbook.vercel.app/url/gitbook.com/docs/creating-content/content-structure/space) linked to them.

You can view all the permissions set for users with access to the docs site from the permissions modal from the docs site’s **Overview** page. You’ll also see which space the user’s permission was inherited from. If you’d like to change the permission settings, open the space, then click **Share**. Here you can edit the permissions from a modal.

Users with **Administrator** or **Creator** permissions on *any* space linked to a specific docs site will have full access permissions for the site. This means that they’ll be able to control any of the publishing and customization settings.

Users with **Reviewer**, **Editor**, **Commenter**, or **Reader** permissions on any space linked to a specific site will get read-only permissions. This means they will see the docs site in your organization, but won’t be able to access any of its settings.
