> For the complete documentation index, see [llms.txt](https://docs.kumu.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kumu.io/frequently-asked-questions/how-do-i-rename-map-view.md).

# How do I rename my map/view?

By default, each new map or view is named "Untitled Map"/"Untitled View". To change the name of your map or view, follow the steps below. Note that maps and views should have unique names.

## Rename your map

1. Click on the tree dots in the top-right corner of your map description > click "Map" > choose "Rename Map".
2. OR, right-click with your mouse on any blank space in your map > click "Map" > choose "Rename Map".

## Rename your view

1. Click on the Settings button of your map to open the Basic Editor on the right. Then click on the tree dots in the top-right corner of your Basic Editor > click "View" > choose "Rename View".
2. OR, right-click with your mouse on any blank space in your map > click "View" > choose "Rename View".


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.kumu.io/frequently-asked-questions/how-do-i-rename-map-view.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.