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

# Projects in Chevre: Organize Your Workflows Effectively

> Projects group related workflows and resources within a workspace. Learn how to create, configure, archive, and delete projects in Chevre.

Projects organize related workflows and resources within a workspace. Think of a project as a folder for a specific team, product area, or use case — a place where all the workflows, automations, and run history relevant to one context live together. By grouping your work into projects, you make it easier for the right people to find what they need and for everyone else to stay out of what they don't.

## What a Project Contains

Each project in Chevre holds the following resources:

| Resource        | Description                                                                        |
| --------------- | ---------------------------------------------------------------------------------- |
| **Workflows**   | The step-by-step processes your team defines and runs within this project.         |
| **Automations** | Triggers and rules attached to workflows that cause them to execute automatically. |
| **Run History** | A log of every workflow execution — its status, duration, inputs, and outputs.     |
| **Settings**    | Name, description, color label, visibility, and other project-level configuration. |

## Creating a Project

<Steps>
  <Step title="Go to the workspace dashboard">
    Navigate to the **Home** tab of your workspace. You'll see a list of existing projects and a button to create a new one.
  </Step>

  <Step title="Click + New Project">
    Click the **+ New Project** button in the top-right corner of the project list. The project creation panel slides open.
  </Step>

  <Step title="Name your project">
    Enter a name that clearly identifies the team, product area, or use case this project covers. Names must be unique within a workspace.
  </Step>

  <Step title="Add a description (optional)">
    Write a short description to help teammates understand the project's purpose. This appears on the project card and in search results.
  </Step>

  <Step title="Choose a color label">
    Pick a color from the palette to visually distinguish this project from others in the dashboard sidebar and project list.
  </Step>

  <Step title="Set visibility">
    Choose **Shared** to make the project visible to all workspace members, or **Private** to restrict access to invited members only. See [Project Visibility](#project-visibility-and-access-control) for details.
  </Step>

  <Step title="Create the project">
    Click **Create Project**. Chevre creates the project and opens it in the workflow editor, ready for you to add your first workflow.
  </Step>
</Steps>

## Project Settings

Update a project's settings at any time by opening the project and navigating to **Settings** in the left sidebar.

| Setting         | Description                                                                                  |
| --------------- | -------------------------------------------------------------------------------------------- |
| **Name**        | The display name for the project, shown in the sidebar and dashboard.                        |
| **Description** | A short summary of the project's purpose. Supports plain text only.                          |
| **Color Label** | A color tag that appears next to the project name in the sidebar and project list.           |
| **Visibility**  | Controls whether the project is visible to all workspace members or only to invited members. |

<Tip>
  Use color labels consistently across your workspace to make visual scanning faster. For example, assign red to production-critical projects, yellow to work-in-progress, and green to stable, low-touch automations. Your team will learn the system quickly and spend less time hunting for the right project.
</Tip>

## Archiving vs. Deleting Projects

Chevre gives you two ways to retire a project you no longer actively use. Choose the right option based on whether you need to preserve the project's history.

<Tabs>
  <Tab title="Archive a Project">
    Archiving a project hides it from the active project list and prevents any automations within it from running. All workflows, run history, and settings are preserved and can be restored at any time.

    To archive a project, open **Settings** inside the project, scroll to the **Project Status** section, and click **Archive Project**. Archived projects appear under the **Archived** filter in the workspace dashboard.

    To restore an archived project, find it under the **Archived** filter, open its settings, and click **Restore Project**.
  </Tab>

  <Tab title="Delete a Project">
    Deleting a project permanently removes it along with all its workflows, automations, and run history. This action cannot be undone.

    To delete a project, open **Settings** inside the project, scroll to the **Danger Zone** section, and click **Delete Project**. Confirm by typing the project name in the prompt.

    Only workspace **Owners** and **Admins** can delete projects. Editors can archive projects they have access to, but cannot delete them.
  </Tab>
</Tabs>

## Project Visibility and Access Control

Project visibility determines which workspace members can see and interact with a project's workflows.

| Visibility  | Who can access it                                                                                                             |
| ----------- | ----------------------------------------------------------------------------------------------------------------------------- |
| **Shared**  | All current and future members of the workspace can view the project. Members with Editor or higher roles can edit workflows. |
| **Private** | Only workspace Owners, Admins, and members explicitly added to the project can access it.                                     |

Private projects are ideal for sensitive workflows, early-stage work, or processes that only a subset of your team should see. When you set a project to **Private**, it disappears from the project list for anyone who hasn't been added to it.

For a full explanation of how workspace roles and project-level access interact, see [Members & Permissions](/concepts/members-permissions).