# Site settings

{% hint style="info" %}
Certain customization features are only available on [Premium and Ultimate site plans](https://www.gitbook.com/pricing).
{% endhint %}

<figure><img src="/files/FAaYfZWBPcbViZwN7IrL" alt="A GitBook screenshot showing site settings"><figcaption><p>Update the settings for your published documentation.</p></figcaption></figure>

### General

<details>

<summary>Site title</summary>

Change the name of your site, if you don't have a custom logo this is the name that your site visitors will see.

</details>

<details>

<summary>Analytics cookie</summary>

If you want to use GitBook’s [site analytics](/docs/docs-site/insights.md), your site will use cookies to identify returning visitors and gather the data needed to view your analytics.

You can choose to disable these cookies, but it will prevent you from using site analytics.

</details>

<details>

<summary>Unpublish site</summary>

Unpublish your site, but keep its settings and customizations. You can publish your site again at any time.

</details>

<details>

<summary>Delete site</summary>

Unpublish and remove your site from the **Docs site** section in the GitBook app.

**Note:** Deleting a site is a permanent action and cannot be undone. Any settings and customizations will be lost, but your content will remain in its [space](/docs/creating-content/content-structure/space.md).

</details>

<details>

<summary>Access</summary>

Manage who can access and administer your docs site.

Open **Access** and click **Manage permissions**. You can also use **Share** from the site’s **Overview** page.

Site permissions are available on all plans.

By default, new sites derive permissions from their linked [spaces](/docs/creating-content/content-structure/space.md), until you update permissions from the site permissions modal.

Site permissions can also affect the permissions of linked spaces that use **Inherited** mode. In this case, each inherited space receives the highest permission level granted by the organization, any parent collection, and any site that includes it.

</details>

### Agents

{% content-ref url="/pages/QEdtUjQ47A0aK7o8HIzN" %}
[What is GitBook Agent?](/docs/gitbook-agent/what-is-gitbook-agent.md)
{% endcontent-ref %}

### Audience

<details>

<summary>Audience</summary>

Choose who sees your published content. See [Publish a docs site](/docs/docs-site/publish-a-docs-site.md) for more info.

</details>

<details>

<summary>Adaptive content <mark style="background-color:purple;">Ultimate</mark></summary>

Turn on adaptive content for your site pages, variants, and sections. [Adaptive content](/docs/site-access/adaptive-content.md) lets you hide or show content for different visitors, depending on their permissions.

Your visitor token signing key will also be displayed here.

</details>

### Domain and URL

<details>

<summary>Custom domain</summary>

Configure a custom domain to unify your site with your own branding. See [Set a custom domain](/docs/docs-site/custom-domain.md) for more info.

</details>

<details>

<summary>GitBook Subdirectory</summary>

Publish your content on a subdirectory (e.g. `yourcompany.com/docs`). See [#gitbook-subdirectory](#gitbook-subdirectory "mention") for more info

</details>

### Redirects

{% content-ref url="/pages/rcmnyzKOgcYE9OgyZD2Y" %}
[Site redirects](/docs/docs-site/site-redirects.md)
{% endcontent-ref %}

### Features

<details>

<summary>PDF export <mark style="background-color:purple;">Premium &#x26; Ultimate</mark></summary>

Let your visitors to export your GitBook as PDF. See [PDF export](/docs/docs-site/pdf-export.md) for more info.

</details>

<details>

<summary>Page ratings <mark style="background-color:purple;">Premium &#x26; Ultimate</mark></summary>

Choose whether or not visitors to your published content can leave a rating on each page to let you know how they feel about it. They’ll be able to choose a sad, neutral, or happy face.

You can review the results of these ratings by opening [site analytics](/docs/docs-site/insights.md) from your docs site dashboard and selecting **Pages & feedback**.

</details>

### AI & MCP

<details>

<summary>Choose the AI experience <mark style="background-color:purple;">Ultimate</mark></summary>

Let your site visitors ask GitBook anything with AI search or the GitBook assistant. See [AI Search](/docs/docs-site/ai-search.md) for more info.

</details>

<details>

<summary>Extend it with MCP connectors <mark style="background-color:purple;">Ultimate</mark></summary>

Configure MCP servers that the AI assistant can use when answering user questions inside your docs. See [AI Search](/docs/docs-site/ai-search.md#how-do-i-use-gitbook-ai) for more info.

</details>

### Connections

{% content-ref url="/pages/p6K5x8aCszGQ0xYf96Z2" %}
[Connections](/docs/ai-and-search/connections.md)
{% endcontent-ref %}

### Structure

{% content-ref url="/pages/1XRw1GP3RDSWHxEE1tQb" %}
[Site structure](/docs/docs-site/site-structure.md)
{% endcontent-ref %}

### Plan

{% content-ref url="/pages/yshuePqcxELaw0iNFK7a" %}
[Plans](/docs/account-management/plans.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gitbook.com/docs/docs-site/site-settings.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.