> 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/guides/views.md). # Views A [view](/overview/kumus-architecture.md#views) is a collection of decorations, filters, and other settings that change what is visible on your map and how it is styled. You can create any number of views, and a view can apply to multiple maps (a map defines the elements and connections that should be part of a map, and their positions on the map). {% embed url="" %} ## Creating a new view Use the navigation at the top of your map and click the view dropdown menu on the right. Click "+ new view" and give the view a name. ## Switching views Switch between views using the navigation at the top of your map. You can also use a [view toggle control](/guides/controls/view-toggle-control.md) to allow readers to switch between [partial views](/guides/partial-views.md). ## Editing a view To edit a view, first select the view in the dropdown at the top of your map. Then, you can use the [Basic or Advanced Editor](/overview/user-interfaces/view-editors.md) to make changes to it. ## Renaming, duplicating, or deleting a view If you want to rename or delete a view, first select the view in the dropdown at the top of your map. Then click the settings button to open the sidebar and then click the more menu (...) in the upper right corner. You can then choose to: * Rename view * Duplicate view * Delete 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.kumu.io/guides/views.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.