> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/maps/organize-maps.md).
# Organize maps
Find, rename, and delete your Felt maps and drafts. Organize maps into projects and folders.
Felt keeps every map in a workspace, either in your **Drafts** or in a project. To find a map, use the sidebar on the [workspace home page](https://felt.com/).
## Find your maps
The sidebar on the home page has four places to find a map:
* Recent maps: maps you've recently viewed or edited. Use the dropdown menu at the top to switch between **My maps**, **Workspace maps**, and **All maps**.
* Search: finds maps and folders in the workspace by title, and maps by description.
* Drafts: maps you've created in this workspace that aren't in a project yet.
* Projects: each project you can see in the workspace.
New drafts are private unless your [Enterprise workspace settings](/administration/workspaces.md#enterprise-settings) set a different default for public link access. Click **Share** to check or change who can open a draft. See [Share a map](/share/share-a-map.md).
To go back to the home page from a map, open the **Felt** menu and click **Home**.
## Delete a map
Deleting a Felt map removes the map and its layers, annotations, and comments for everyone. You need Edit access to the map's project, or the map must be in your **Drafts**.
{% hint style="danger" %}
You can't restore a deleted map yourself. Support can restore it if you contact within 7 days. To keep an independent backup, duplicate the map and turn off **Sync** on the copy's Felt Server layers. See [How copies stay in step](/layers/copy-and-duplicate-layers.md#how-copies-stay-in-step).
{% endhint %}
1. Open the map.
2. Open the **Felt** menu and click **File** > **Delete map…**.
3. Confirm. Felt deletes the map and takes you back to the home page.
## Rename a map
To rename a map, click **Edit map** in the toolbar at the top right of the map, then click the title at the top left. Enter a new name and press **Enter**.
## Projects
A project is a group of Felt maps in a workspace, and it controls who can see and edit them. Every workspace starts with a project named **General** that's open to the workspace.
* A project open to the workspace automatically includes every workspace member. Each member gets their workspace access level, limited by the project's default access.
* Only invited people can see a private project. Other members don't see it in the sidebar.
You can invite workspace members and external collaborators to either kind. External collaborators see only the projects and maps they're invited to. See [Permissions](/administration/permissions.md).
### Create a project
To create a Felt project, you need Edit or Admin access to the workspace. You get Project admin access to the projects you create.
1. On the home page, click **New project** (the folder icon with a plus) next to **Maps** in the sidebar. The **+** next to it is **New map**.
2. In **Name**, enter a name for the project.
3. Under **Access**, select **Workspace** or **Private**.
4. Optional: For a **Workspace** project, select a **Default access**: **View**, **Contribute**, or **Edit**.
5. Click **Create**.
### Share a project
You need Project admin access to change a project's default access or whether it's open to the workspace. To share a project, click **Share** at the top right of its page, invite people by email, and set their access.
To make a project private, click **Share**, select **None (make private)** next to the workspace's name, and click **Make private**. To open it to the workspace again, select **View**, **Contribute**, or **Edit** next to the workspace's name, and click **Open to workspace**.
### Rename or delete a project
To rename a Felt project, you need Edit access to it. Click its name at the top of the project page, enter a new name, and press **Enter**.
To delete a project, you need Project admin access. Open the **···** menu at the top right of the project page and click **Delete project**.
{% hint style="danger" %}
Deleting a project also deletes every map and folder in it, and you can't undo the deletion. To keep some maps, move them to another project first.
{% endhint %}
## Folders
A folder groups Felt maps inside a project and can contain other folders. Folders have no access settings of their own, so everyone with access to the project can open the maps in its folders. To limit who sees some maps, put them in a separate project.
To create a folder, open the project and click **New folder** at the top right. To put a map in a folder, move the map and select the folder under its project in the **Move map** dialog. See [Move a map within a workspace](/maps/duplicate-and-move-maps.md#move-a-map-within-a-workspace).
To rename, move, or delete a folder, open the folder, then open the **···** menu at the top right and click **Rename folder**, **Move folder**, or **Delete folder**. Deleting a folder also deletes the maps and folders in it.
---
# 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://help.felt.com/maps/organize-maps.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.
