> 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/urls.md).

# URLs

Kumu URLs follow a predictable pattern: every URL starts with `https://kumu.io` and ends with one of the options described in the table below. When you're visiting Kumu links or sending them to your friends, colleagues, and collaborators, the information below will help you know exactly what you're linking to.

{% embed url="<https://www.youtube.com/watch?v=iORN_mRpkMI>" %}

{% hint style="info" %}
*Before you dive in: if you're not sure what we mean by `slug` in the table below,* \
*check out* [*our full guide on slugs*](/guides/slugs.md)*.*
{% endhint %}

| Link's destination                                                                        | URL format                                                                                                 |
| ----------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Your account dashboard                                                                    | `/dashboard`                                                                                               |
| Your account settings                                                                     | `/settings`                                                                                                |
| A workspace's dashboard and settings                                                      | `/<workspace name slug>/settings`                                                                          |
| A public Kumu profile                                                                     | `/<username>`                                                                                              |
| A Kumu project                                                                            | `/<workspace name slug>/<project name slug>`                                                               |
| A specific map in a project                                                               | `/<workspace name slug>/<project name slug>#<map name slug>`                                               |
| A specific map with a specific view applied                                               | `/<workspace name slug>/<project name slug>#<map name slug>/<view name slug>`                              |
| A specific element or loop in a map, with the default view applied                        | `/<workspace name slug>/<project name slug>#<map name slug>/<element or loop label slug>`                  |
| A specific element or loop in a map, with a different view applied (not the default view) | `/<workspace name slug>/<project name slug>#<map name slug>/<view name slug>/<element or loop label slug>` |


---

# 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/urls.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.