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

# Project

> Organize database resources, member permissions, and changes for an application or team.

A **Project** is a space within a Bytebase workspace where a team manages its database resources and changes. It brings together databases, any instances owned by the project, member roles, and the Plans and Releases used to deliver changes. Project settings control access and the change workflow.

For example, an HR team can have one project for its Test and Prod databases. The team manages both in the same project while applying different policies to each environment. A project can include databases hosted on different instances.

## Create a project

A Workspace Admin, Workspace DBA, or member with project-creation permission opens **Projects → Create**, enters a name and project ID, and clicks **Create**. The creator becomes a Project Owner and can manage the project's members and settings.

Creating a project creates the organizational space in Bytebase. Database servers and databases are registered or assigned separately.

## Add resources and members

Bring resources into the project so the responsible team can manage their access and changes together:

* **Databases:** assign or transfer existing databases from workspace instances. Assignment determines which project manages a database.
* **Instances:** register a project instance when the project should manage the instance and all its databases. See [instance scope](/concepts/instance#workspace-and-project-instances) for the ownership and transfer rules.
* **Members:** grant project roles to users or groups according to their responsibilities, such as authoring changes, reviewing them, or deploying them.

Each database belongs to one project. A database discovered on a workspace instance can appear under **Unassigned** until it is assigned to a team's project.

## Work in a project

Select the project from **Projects** or the project switcher:

| Area                     | What you do there                                            |
| ------------------------ | ------------------------------------------------------------ |
| **Databases**            | Inspect the project's databases and open them in SQL Editor. |
| **Instances**            | Manage instances owned by the project.                       |
| **CI/CD → Plans**        | Propose changes and follow their review and deployment.      |
| **CI/CD → Releases**     | Inspect the SQL files packaged for deployment.               |
| **Members and settings** | Manage roles and configure the project's workflow.           |

The available actions depend on your permissions. Visibility of a database does not itself grant query access; querying requires a role such as **SQL Editor Read User**. See [database access roles](/security/database-permission/request).

Follow [Create a Project](/get-started/step-by-step/create-a-project) for a short setup example, or [Organize Resources](/onboarding/organize-resources#project) for guidance on choosing project boundaries.