import { Heading } from '@/components/Heading'

# Project setup

<p>
  Projects let you manage teams and tasks within your Workspace. After creating
  your [Workspace](/workspace), you will need to create a new project.
</p>

<Note>
  Before inviting a user to a project, you'll need to invite them to the
  workspace. Then, you can choose to add them to the project from the list of
  users on the workspace.
</Note>

<Heading level={2} id="project-attributes">
  Key project attributes
</Heading>

Every project comes with two key attributes that make it easier to plan and set permissions for users on the workspace.

1. **`Identifier`**: The project identifier is attached to every issue in the project to make it easier to track and differentiate each issue across projects and the workspace.

<Note>
  You can always choose to update your identifier. This will only replace the ID
  string on the issue, but not the number next to it. Note that identifiers can
  only contain uppercase text and no special characters or numbers.
</Note>

These options can be found under the `General` tab inside `Project>Settings` ⬇️

`<project-name>/projects/<id>/settings`.

2. **`Network`**: To restrict other users on the workspace, you can set the network of the project to either Private or Secret. When made public, all users on the workspace can choose to join the project. When set to secret, admins need to invite workspace members to join the project.

<Heading level={2} id="project-controls">
  Project controls
</Heading>

When working on multiple projects, you can set project controls to make it
easier. These controls include a project lead and default issue assignee.

- **Project lead**: The project lead will help you identify and connect with the project leader to make it easier for you to assign tasks or communicate.

- **Default issue assignee**: Everything inside a project is broken down into [issues](/issues). If you want every issue to be assigned, you can choose to set a default assignee for times when an issue is created without any assignees

These options can be found under the `Control` tab inside `Project>Settings` ⬇️

`<project-name>/projects/<id>/settings/control`.

<Heading level={2} id="project-controls">
  Project members
</Heading>

When the project is set to the `Public` network under project controls, it is open to all members on the workspace. When set to `Secret` network, workspace members must be invited to the project to gain access.

For every member that is invited to the project, you can control their roles
just [like on the workspace](workspace/#workspace-roles). All roles (Admin, Member, Guest, Viewer) are
supported.

These options can be found under the `Members` tab inside `Project>Settings` ⬇️

`<project-name>/projects/<id>/settings/members`.

<Heading level={2} id="project-states">
  Project states
</Heading>

To organize issues based on the principles of project management, we allow you
to create custom states in the default grouped states. This will make it
easier to use project views and filtering.

Default states:

- Backlog
- Unstarted
- Started
- Completed
- Cancelled

Inside these default states, you can create as many states as you like based
on the type of default state. In the future, we plan to allow users to create
or customize the default state based on their requirements. Please [raise a
feature request](https://github.com/makeplane/plane/issues) on our issues, if you would like to see this soon.

These options can be found under the `States` tab inside `Project>Settings` ⬇️

`<project-name>/projects/<id>/settings/states`.

<Heading level={2} id="project-labels">
  Project labels
</Heading>

Similar to states, labels on projects help you filter or differentiate issues
within your project. You can create and control as many issue labels as
needed.

<Note>Labels can also be created from the issue detail page.</Note>

These options can be found under the `Labels` tab inside `Project>Settings` ⬇️

`<project-name>/projects/<id>/settings/labels`.

<Heading level={2} id="delete-a-project">
  Delete a project
</Heading>

We restrict the delete access to project admin, _we plan to extend this feature to workspace owners as well_.

These options can be found under the `General` tab inside `Project>Settings` ⬇️

`<project-name>/projects/<id>/settings/general`.

<Note>
  If a project is deleted, all of its content, issues, cycles, and modules will
  also be deleted. Currently, Plane does not offer a automatic backup service on
  cloud or self-hosted versions, but it is planned on our roadmap.
</Note>

<Heading level={2} id="project-shortcuts">
  Project shortcuts
</Heading>

1. Create a new project: `CTRL/CMD + P`

<Heading level={2} id="delete-a-workspace">
  Project plans
</Heading>

- **Cloud**: All-plans, no suggestion, no limits.
- **Self-hosted**: No plans, no suggestion, no limits.
