> For the complete documentation index, see [llms.txt](https://docs.overleaf.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.overleaf.com/managing-projects-and-files/renaming-a-project.md).
# Renaming a project
There are two ways to rename an Overleaf project:
1. [#from-the-project-dashboard](#from-the-project-dashboard "mention")
2. [#from-within-the-project](#from-within-the-project "mention")
## From the project dashboard
You can select the project in your project dashboard, and then go to **More** > **Rename** above the project list.
## From within the project
Alternatively, if you're currently working on a project, you can click the project name at the top of the editor and the select **Rename** in the dropdown menu that appears:
{% hint style="warning" %}
Note that only the project's owner can change its name.
{% 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.overleaf.com/managing-projects-and-files/renaming-a-project.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.
