> ## Documentation Index > Fetch the complete documentation index at: https://docs.puggy.dev/llms.txt > Use this file to discover all available pages before exploring further. # Projects and session keys > Group sessions into projects, give every session a short key like PUG-134, and filter the list by project. Projects group related sessions, for example by product, area, or team. Every session in a project gets a short **session key**, such as `PUG-134`, that's easy to say in standup, search for, and paste into a ticket. Anyone in the organization can create projects and assign sessions to them. ## Why use projects Without projects, every session in your organization lands in one long list. Projects help once more than one product, team, or stream of work shares a workspace. * **Separate products or apps.** Put sessions for your web app, admin panel, and marketing site in their own projects (`WEB`, `ADM`, `MKT`), so each team filters to its own sessions. * **Talk about a bug by name.** "Can you look at `PUG-134`?" is quicker than pasting a long link or describing the session. Anyone can type the key into search to open it. * **Match your tracker.** Use the same prefix as your Jira or Linear project, so `PAY-42` in Puggy sits naturally next to the `PAY` tickets it was filed to. * **Group a release or test cycle.** Create a project for a release candidate or a regression pass, assign every session found during it, and review them together. Projects are optional. If your team works on one product, you can skip them; search and filters work the same either way. ## What a project has | Field | Details | | - | - | | **Name** | Unique within your organization. | | **Colour** | Indigo, emerald, amber, rose, or sky. Shown as a dot next to the project everywhere it appears. | | **Key prefix** | Exactly three letters, A–Z, unique within your organization. Used at the start of every session key in the project. You can change it later, but that changes every session's key. | ### Session keys A session's key is its project's prefix and a number, for example `PUG-134`. Once a session has a key: * The project selector on the session page shows the key instead of **No project**. * The key is listed on the session's **Info** tab. * Typing the key in the [sessions search box](https://docs.puggy.dev/console/sessions.md#search) jumps straight to the session. * You can open the session directly at its key. ## Assign a session to a project Open the session and choose the project selector at the top of the page. It says **No project** until the session is in one. ![The project selector open, with Find a project, the Puggy project and its PUG prefix, and New project](https://mintcdn.com/anoclap/hpVVUQ1W_GXTEu9W/images/console/project-selector-light.webp?fit=max\&auto=format\&n=hpVVUQ1W_GXTEu9W\&q=85\&s=143be4b26bb7582b0fb52c286c517b32) 1. Type in **Find a project…** to narrow the list. Each project shows its colour and prefix. 2. Choose a project. The session gets the next key in that project. You can also choose a project in the extension's session window right after you record. ## Create a project 1. Open the project selector on a session and choose **New project**. 2. Enter a **Name**. 3. Pick a **Colour**. 4. Check the **Key prefix**. Puggy suggests the first three letters of the name (padded with X if the name has fewer letters, or **PRJ** if it has none). Change it to any three letters; the hint underneath shows how keys will look, for example **PRJ-12**. You can change it later, but that re-keys every session in the project, so pick one you'll keep. 5. Choose **Create and assign**. The project is created and the session is added to it. ![The New project panel with Name, Colour swatches, Key prefix set to PRJ, and Create and assign](https://mintcdn.com/anoclap/hpVVUQ1W_GXTEu9W/images/console/project-new-light.webp?fit=max\&auto=format\&n=hpVVUQ1W_GXTEu9W\&q=85\&s=688969d3591e41adf8dc74100c79b712) If another project already uses the prefix you chose, Puggy creates the project with the suggested prefix instead and tells you. You can change it later by editing the project. ## Move a session or remove its project From the project selector on a session that's already in a project: * **Choose another project** to move the session. Puggy asks you to confirm with **Move to** the project's name, because the session gets a new key and **links using its current key stop working**. * **Remove from session** takes the session out of its project. Puggy asks **Remove the project?** first; the session loses its key and goes back to having no project. > [!WARNING] > > Moving or removing a project changes or removes the session's key. Update any tickets or messages that link to the session by its old key, or share the session's [console link](https://docs.puggy.dev/console/session-details.md#share-menu) instead, which never changes. ## Edit a project Open a session that's in the project, open the project selector, and choose **Edit project**. ![The project selector on a session in the Puggy project, showing the PUG-2 key, with New project, Edit project, and Remove from session](https://mintcdn.com/anoclap/hpVVUQ1W_GXTEu9W/images/console/project-selector-assigned-dark.webp?fit=max\&auto=format\&n=hpVVUQ1W_GXTEu9W\&q=85\&s=4b9028f89dcd4cd6ea3ed3c81341278d) ![The Edit project panel with Name, Colour, and the Change the key prefix checkbox](https://mintcdn.com/anoclap/hpVVUQ1W_GXTEu9W/images/console/project-edit-dark.webp?fit=max\&auto=format\&n=hpVVUQ1W_GXTEu9W\&q=85\&s=ad442ee9f549f4a70f4ea161fa77ef08) * Change the **Name** or **Colour**. * To change the prefix, turn on **Change the key prefix** and enter three new letters. The prefix must not already be used by another project in your organization. * Choose **Save changes**. Changes apply to every session in the project. ## Delete a project Open a session that's in the project, open the project selector, and choose **Delete project**. Puggy asks you to confirm first. The project's sessions are kept, but they go back to having no project and every key with the project's prefix stops working. You can't undo this. > [!WARNING] > > Changing the prefix changes the key of **every session in the project** at once. For example, renaming the prefix from `PUG` to `APP` turns `PUG-134` into `APP-134`, and links, tickets, and messages that use the old keys stop working. Share sessions with their [console link](https://docs.puggy.dev/console/session-details.md#share-menu) if you might change a prefix later; that link never changes. ## Filter the list by project In the sessions list header, choose the filter button next to the project name (it says **All projects** when no filter is set) and pick a project under **Filter by project**. Choose **All projects** to see everything again. ![The Filter by project menu with All projects selected and the Puggy project](https://mintcdn.com/anoclap/hpVVUQ1W_GXTEu9W/images/console/project-filter-light.webp?fit=max\&auto=format\&n=hpVVUQ1W_GXTEu9W\&q=85\&s=3e11412fbd9212638ea49693c0c1cb8f) You can also search for a project's name or prefix in the search box. See [Sessions list](https://docs.puggy.dev/console/sessions.md). ## Limits * A session can be in one project at a time. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.