> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/navigating-the-excel-add-in/setup.md).

# Setup

Install the current add-in, learn the rules of the road, and remove the legacy add-in.

Install the current add-in, learn the rules of the road, and remove the legacy add-in.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Add-in Best Practices</strong></td><td>The rules that keep the add-in and the model in sync.</td><td><a href="/navigating-the-excel-add-in/setup/add-in-best-practices.md">Add-in Best Practices</a></td></tr><tr><td><strong>Install the Drivepoint 2.0 Add-in</strong></td><td>Install the add-in that connects Excel to the web app and the warehouse.</td><td><a href="/navigating-the-excel-add-in/setup/installing-the-drivepoint-2.0-add-in.md">Install the Drivepoint 2.0 Add-in</a></td></tr><tr><td><strong>Remove the Legacy Add-in</strong></td><td>Uninstall Drivepoint Legacy after you move to 2.0.</td><td><a href="/navigating-the-excel-add-in/setup/removing-the-old-add-in-drivepoint-legacy.md">Remove the Legacy Add-in</a></td></tr></tbody></table>


---

# 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.drivepoint.io/navigating-the-excel-add-in/setup.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.