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

# Managing Projects

> How to organize projects in HoneyHive for your AI applications.

A project is the boundary for a single AI application in HoneyHive. All traces, datasets, evaluations, prompts, and metrics live within a project. Each project has its own API key for SDK authentication.

Projects live inside [workspaces](/v2/workspace/organization-hierarchy#workspace). New organizations include a starter workspace and project so you can create an API key and begin tracing immediately. To create another project, navigate to your workspace and click **New Project**. You can also create projects programmatically via the [API](/v2/api-reference/projects/create-a-new-project).

Project names can only contain letters, numbers, and underscores, and must be unique within a workspace.

## Organizing projects

For complex AI pipelines, we recommend creating multiple projects within a workspace:

1. **A production project** (e.g., "Chatbot Production")
   * Source of truth for production traces and CI tests
   * Keep schemas stable and aligned with what runs in production

2. **One project per testable component** (e.g., "Chatbot Retriever")
   * For offline evaluation, prompt management, and experiments
   * Track what worked for a specific piece of the pipeline

3. **A catch-all project** (e.g., "Chatbot Random")
   * For ad-hoc experiments and ideas worth keeping but not actively referenced

## Archiving projects

Projects can be archived when they are no longer actively used. Archiving performs a soft delete -- the project and its data are hidden but not permanently removed. Projects can be archived via the API.

## Access control

Project access is managed independently from workspace access. A user must be explicitly added to a project to see its data -- being a workspace member does not grant automatic access to all projects within it.

* **Project Admins** have full control over the project and its members.
* **Project Members** can view and create most resources but cannot delete them or manage membership roles.

See [Roles](/v2/workspace/roles) for the full permission breakdown.