> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pluvo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Keep a workstream's chats, agents, spreadsheets, context, and artifacts together in one place.

## What it does

A project keeps everything for one workstream together, such as the month-end close, a board pack, or a budget cycle. Its chats, agents, spreadsheets, and artifacts live in the project, alongside the metrics, tables, skills, and rules it relies on.

Every chat and agent run inside a project works with that context automatically. The Assistant prefers the project's metrics and tables when they fit, follows its rules, and draws on its skills, so you do not have to explain the workstream again each time.

## Creating a project

**1. Open Projects**

Choose **Projects** in the sidebar, then **New project**.

**2. Name it**

Give it a **Name**, such as "Month-end close", and optionally a **Description** of what the workstream covers and what done looks like. Names must be unique in your organization, archived projects included.

**3. Create it**

Choose **Create project**. You become its owner and land on its overview.

To give a project its own look, click its icon in the header and pick a colour and an icon.

## Finding your projects

The **Projects** page lists every project you can see, with its owner and members. Switch between **All projects**, **Starred**, and **Mine**, search by name or description, and choose **Archived projects** to see ones that are no longer active.

Star a project to keep it at hand. Starred projects also appear in their own section of the sidebar.

## Inside a project

When you open a project, the sidebar switches to show just that project: its **Overview**, **Agents**, **Spreadsheets**, **Library**, and **Artifacts**, followed by its chats. **All projects** takes you back.

The **Overview** has a message box for asking about the project, the latest agent runs, and the project's chat history. Cards on the right summarize its properties, its Library, its agents and spreadsheets, and its members.

### Chats

Chats started from the project's overview belong to the project. They appear in the project's sidebar rather than in your main chat list, though chat search still finds them. Choose **+** beside **Chats** to start another.

### Agents, spreadsheets, and artifacts

Anything you create from inside a project is filed there:

* **Agents** created with **New agent** on the project's Agents page. See **Agents**.
* **Spreadsheets** created with **New spreadsheet** or **Import .xlsx**, or made by the Assistant in a project chat.
* **Artifacts** made in the project's chats or by its agents. **New artifact** starts a project chat to build one. Project artifacts also appear in the main Artifacts list.

The main **Artifacts**, **Spreadsheets**, and **Agents** lists have a **Project** column and filter, so you can see which project each item belongs to.

## Giving a project its context

The project's **Library** has four tabs, and everything in them shapes the project's chats and agent runs.

* **Metrics** and **Tables**: choose **Add metric** or **Add table** to link approved ones from your Library. The Assistant uses these first when they fit.
* **Skills**: choose **New skill** to write one just for this project, or **Add skill** to link one from your Library. Project skills are visible to everyone in the project and editable by its editors.
* **Rules**: choose **Add rule** and give it a title and the instruction. The Assistant follows project rules in every chat and agent run in the project, on top of your organization's rules. A project's rules can total up to 20,000 characters.

Linked items stay in your Library. Choose the **X** beside one to remove it from the project.

> [!TIP]
>
> Use project rules for things that only matter to this workstream, for example "Before proposing any write-back to the accounting system, ask the project owner to approve it." Keep organization-wide rules in the main Library.

## Sharing a project

Choose **Share** on the project overview. Add people as **Viewer** (can view) or **Editor** (can view and edit), or turn on **Share with organization** so anyone in your organization can view it. Guests can only be added as Viewers.

Members see the project, its project skills, and the artifacts and spreadsheets shared with it. When something is made in a project, its share dialog has a **Share with** switch for that project, on by default, so project members can view it. Turn it off to keep an item to yourself. Skills linked from your Library are shared with project members only if the skill's **Automatically share with project members** switch is on.

Project access is view-only for the items inside. To let someone edit a particular artifact or spreadsheet, share it with them directly.

> [!NOTE]
>
> Agents are not shared. Each person sees only their own agents, including on a project's Agents page. If an editor who owns agents is moved to Viewer or removed, Pluvo warns you first, and their agents pause until they can edit the project again.

## Editing and archiving

From the **⋯** menu on the overview:

* **Edit details** changes the name and description.
* **Archive project** makes the project read-only. Members can still open it, but new chats, changes, and scheduled agent runs stop until it is restored.
* **Restore project** brings an archived project back.

## Tips

> [!TIP]
>
> Set up the project's Library before you start chatting. Linking the right metrics and tables and adding a rule or two gets better answers from the first question.

> [!TIP]
>
> Use the **Project** filter on the main Artifacts and Spreadsheets lists to pull together everything a workstream has produced.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.