# Adaptive content

{% hint style="info" %}
This feature is available on the [Ultimate site plan](https://www.gitbook.com/pricing).
{% endhint %}

When a user visits your site, you may already know things about them — such as who they are, which plan they’re subscribed to, and which features they have access to.

Adaptive content helps to build a tailored documentation experience based on who is reading.

<figure><img src="/files/SDCdvkYUUhl40kpwCiNN" alt="A GitBook screenshot showing adaptive content controls"><figcaption><p>Personalize your user’s documentation experience through adaptive content</p></figcaption></figure>

<p align="center"><a href="https://gitbook.com/adaptive-content-demo/" class="button primary">Launch the demo site</a></p>

{% hint style="info" %}
Adaptive content is slightly different from [authenticated access](/docs/site-access/authenticated-access.md), although they can work together.

While authenticated access allows you to protect your docs through a login, adaptive content customizes published material based on various authentication methods — including authenticated access or those from your own app.
{% endhint %}

### How it works

Adaptive content works in one of two ways:

1. Passing data from your app to GitBook
2. Passing data from authenticated access

When a user visits your sites, we call the data they bring with them their “claims” — basically data that helps to identify a user. These claims are controllable by you — the site author — and can be used through the GitBook editor to show or hide different pages, variants, and sections in your docs.

Head to our page about [enabling adaptive content](/docs/site-access/adaptive-content/enabling-adaptive-content.md) to start setting up adaptive content for your site.


---

# 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/site-access/adaptive-content.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.