> ## 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 > Understand how HUD Projects organize environments and tasksets. A HUD **Project** is the workspace boundary for a related set of environments and tasksets. Projects also control who can see those resources and who can create new ones. Projects is currently a limited beta. If it is not enabled for your team, Project-specific CLI commands stop with a message explaining how to request access; normal deploy and task sync workflows continue to use the team default Project. ## Default Project Every team has a default Project. If you deploy an environment or publish a taskset without choosing another Project, HUD places it in the team default. This keeps the normal workflow zero-configuration. ## Project selection A local environment directory can be associated with a Project. Deploys and task syncs from that directory then use the same destination, keeping an environment and its tasksets together. For automation or exceptional cases, a command can select a different destination explicitly without changing the directory association. A machine-wide preference can provide a fallback for directories without an association. Project selection only controls where a **new** resource is created. It does not move resources between Projects. ## Resource ownership Each deployed environment or taskset belongs to one Project. If you need the same resource in another Project, create it there under a separate name rather than changing the Project of the existing resource. Projects may be writable or read-only for a given user. Only team admins can create Projects.