> ## Documentation Index > Fetch the complete documentation index at: https://docs.hud.ai/llms.txt > Use this file to discover all available pages before exploring further. # Projects > Group environments, tasksets, and jobs into projects, and control who can see, create, review, and manage them. A project is a workspace inside your team. It holds environments, tasksets, and jobs, and decides who can see and change them. Use projects to separate benchmarks, customers, or groups of task authors, and give each person the access their role needs. Projects are in limited beta. Until they are enabled for your team, everything is in the Main project and the project controls on this page are hidden. To enable them, [contact HUD](mailto:founders@hud.ai). ## What a project holds Environments, tasksets, and jobs each belong to one project. Everything inside them belongs there too: builds and templates with their environment, tasks with their taskset, and traces with their job. * **A task and its environment share a project.** A task's template must come from an environment in the same project as the task's taskset. * **Resources stay in their project.** To use an environment or taskset in another project, create it again there under its own name. * **New resources go to the current project.** In the web app, that is the project selected in the header; with **All projects** selected, it is the Main project. From the CLI, `hud deploy`, `hud sync tasks`, and `hud harbor import` use `--project`, the directory's project from `hud project use`, or `HUD_DEFAULT_PROJECT`, and otherwise the Main project. See [`hud project`](/v6/reference/cli#hud-project). ## The Main project Every team has a Main project, named after the team, such as `hud-main`. It holds everything the team created before it had other projects. You can rename it but not delete it. Every team member has **Create** on the Main project, and team members with the External role have **Contributor**. Other projects start with no team-wide access: only their creator, team admins, and the people you add can open them. ## Switch and create projects The project switcher in the page header selects the current project. Catalogs such as **Tasksets** and **Environments** list what is in it; **All projects** lists everything you can see. **Create project** in the switcher opens **New project**: enter a name and an optional description. Only team admins can create projects. **Manage projects** lists every project you can see. ## Project scopes Each person in a project holds one scope. Each scope includes everything the scopes above it allow. | Scope | Allows | | - | - | | **Contributor** | Create and manage your own work. Other resources are visible only when shared with you. | | **View** | Create and manage your own work, and view everyone else's resources in this project. | | **Create** | View, create, edit, and run work throughout this project. | | **Review** | Everything in Create, plus review tasks and approve work that is ready. | | **Manage** | Everything in Review, plus manage project settings, access, and resources. | A project's creator and the team's admins have **Manage** without being added. A project scope covers every taskset in the project; [sharing a taskset](/platform/tasksets#share-a-taskset) can raise someone's access to that one taskset, but not lower it. The [task lifecycle](/platform/task-lifecycle#change-a-status) lists which status changes need Create and which need Review. ## Give people access Open **Settings** → **Access** with the project selected. **Your role** shows your scope and where it comes from. With Manage, you also see everyone with access: * **Add to project** grants a scope to members of your team, who get an email. Only team members can be added; [invite people to the team](/platform/team#invite-people) first. To give someone outside your team access to a single taskset, [invite them by email](/platform/tasksets#share-a-taskset). * Select people to **Set scope**, **Remove** their access, or **Copy names** and **Copy emails**. * The Main project's **Default access for all team members** entry can't be changed or removed. ## Project Overview **Project Overview** appears in the sidebar when you have Review or Manage on the current project. The **Overview** tab tracks the project's tasks: * **Project insights**: **Verified**, **Average score**, **Valid runs**, and **QA complete**, with breakdowns by **People** and **Models**. * A table of every task with its assignee, taskset, environment, template, and the spread of scores from valid runs of its latest version. Filter by assignee (including unassigned), model, taskset, or environment, and sort by recent updates, name, or score. Filtering by a model limits each task's scores and QA results to that model. The **Review** tab has two sections: * **Ready for review**: the [review queue](/platform/task-lifecycle#the-review-queue) of tasks waiting on you. * **Contributors**, with Manage: each person's tasks, waiting on review, verified, and needing revision, over the last 7, 30, or 90 days. ## Project settings **Settings** → **Project** shows the project's ID and how many tasksets, environments, and jobs it holds. With Manage, you can change its name, which is also its slug, and its description. To delete a project, delete its resources first, then select **Delete project**. Its participants lose access immediately, and deletion cannot be undone. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.