> 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/using-the-web-app/plans/changing-names-and-plan-folder-associations.md).
# Changing Names and Plan/Folder Associations
It's helpful to understand the Sharepoint UI to make use of certain actions that are not (yet!) available in the Drivepoint interface.
### Changing the name of a Plan
1. Open the Plan in Excel
2. Change the name on the top left of the screen
3. Success - Drivepoint will pick up the naming changes momentarily
### Changing the name of a folder
1. Open your company's Sharepoint ([https://bainbridgegrowth.sharepoint.com/sites/COMPANYNAME/SitePages/CollabHome.aspx](https://bainbridgegrowth.sharepoint.com/sites/FlavorFusion/SitePages/CollabHome.aspx))
2. Click on "Documents" on the left sidepanel
3. Click on "\_\_plans\_\_"
4. Click on the three dots next to the folder you want to rename
5. Rename the folder and confirm
6. Success - Drivepoint will pick up the naming changes momentarily
### Moving a Plan to a different folder
1. Open the Plan in Excel
2. Click on the top left of the screen
3. Click on the > arrow
4. Click on the folder you want to move the Plan to
5. Click "Move Here"
6. Congrats - Drivepoint will pick up your changes momentarily
{% hint style="info" %}
Do NOT move the file outside of **\_\_plans\_\_** since Drivepoint won't know about the Plan anymore.
{% endhint %}
---
# 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/using-the-web-app/plans/changing-names-and-plan-folder-associations.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.
