> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/features/tableau-extension/configuration/schemas/general-configuration/overview-message.md).

# Overview message

When the overview has nothing to show, the extension falls back to a standard empty-state message. That message is generic on purpose, so it rarely explains *why* a user is looking at an empty table: no mark is selected yet, the filters exclude everything, or the user has no read permission on the schema. On the **Overview Message** tab you replace it with your own rich-text message.

The tab is available on all three module types. Open **Worksheet-schema**, pick your schema, stay on the **General** tab and select **Overview Message**.

<figure><img src="https://3247237607-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0gkOLIfzuEyMP2kvoT9o%2Fuploads%2Fgit-blob-a1a56edfeebedf973c16054e75916d21b67c358f%2FWBE634_Ext_Config_OverviewMessage.png?alt=media" alt=""><figcaption><p>The Overview Message tab with the editor open</p></figcaption></figure>

### Write your own message

1. Switch on **Enable custom overview message**.
2. Write the message in the editor. It accepts bold, italic, underline and strikethrough text, links, bullet and numbered lists, text colour, font size and images.
3. Click **Save** in the toolbar. Like every other configuration change, the message is only stored once you save.

Keep it short and tell the reader what to do next — "Select a region on the map to see its targets" beats "No data available".

The message replaces the empty state only. As soon as a row is visible the overview takes over, so a user who can see data never reads it.

### When your message appears

* No mark is selected and **Clearing the selection will** is set to **Exclude all data**.
* The selected mark has no matching rows in the schema.
* A filter under **Filter options**, or an **Allow edit when** rule, leaves nothing to show.
* The logged-in user has no read permission on the schema.

Because a missing read permission looks exactly like an empty result, it is worth naming both possibilities in the text — "Nothing to show. If you expected data here, ask your administrator whether you have access to this schema."


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infotopics.com/features/tableau-extension/configuration/schemas/general-configuration/overview-message.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
