> 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/writebackextreme/features/tableau-extension/configuration.md).
# Configuration
Integrating your extension into the dashboard allows you to refine its appearance and functionality. Initially, adjust the extension's connection settings to link it with a spreadsheet that shares the same Database Table as your schema, specifically the "Missing Orders" sheet within the dashboard. This sheet archives records by a unique identifier, "id." In the following steps, we'll demonstrate how to connect the "Missing Orders" sheet to your extension using "id" as the unique linking dimension.
To integrate the extension with a sheet in the dashboard, follow these steps:
1. Select the field you want to connect to on the dashboard. For this example, choose the “id” field, which is also a hidden column in the “Missing Orders” sheet.
2. Choose the specific sheet to connect to. In this example, it's the “Missing Orders” sheet.
3. Click on the pencil icon to edit.
4. Access the extension settings by clicking on the configuration wheel icon.
---
# 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/writebackextreme/features/tableau-extension/configuration.md?ask=&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.
