# 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-q67etdj25-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.

A GitBook screenshot showing the docs sites homepage — GitBook's docs sites homepage.

### 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-q67etdj25-gitbook.vercel.app/url/gitbook.com/docs/publishing-documentation/site-settings). There are three primary options to choose from when publishing your site:

		Cover image		Cover image (dark)	Cover image (dark)	Cover image (dark)
Public	Publish your docs publicly to the web.	25_12_12_public.png	public-publishing	25_12_12_public_1.png		25_12_12_public_1.png
Privately with share links	Publish your docs with private share links.	25_12_12_share_links_1.png	share-links		25_12_12_share_links.png	25_01_06_share_links@2x.png
Authenticated Access	Protect your published docs behind an OAuth sign in.	25_12_10_auth_access_1.png	authenticated-access			25_12_10_auth_access.png

### 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-q67etdj25-gitbook.vercel.app/url/gitbook.com/docs/site-settings#delete-site) from the top-right corner. ### Site permissions Admins can manage site permissions directly from a docs site. From the site’s **Overview** page, click **Share** in the top-right corner. You can also open **Settings** > **General** and click **Access** > **Manage permissions**. You can also manage these settings from [Site settings](https://gitbook-v2-q67etdj25-gitbook.vercel.app/url/gitbook.com/docs/publishing-documentation/site-settings). Setting a permission level on a site, for everyone, a team, or an individual user, determines their ability to administer or view the site. When spaces within the site are set to ***Inherited*** mode, these permissions are also propagated to those spaces. The table below summarizes how each role maps to permissions on the site and how it propagates to spaces in ***Inherited*** mode. | Permission level for spaces | Permissions on the site | | --------------------------- | ----------------------- | | Administrator | Edit and see | | Creator | See | | Reviewer | See | | Editor | See | | Commenter | See | | Viewer | See | | No access | Cannot see | {% hint style="info" %} Spaces in ***Inherited*** mode inherit permissions from the organization or their parent collection, along with the site permissions and any local overrides. Each member is assigned the highest role they have across these permission sources. {% endhint %}