Projects
A project is a body of work with its own members, states, labels and settings — a product, a team, a workstream. Work items live in exactly one project, so how you split projects is the biggest structural decision you'll make.
What you can do
- Create projects and give each one a permanent short ID (
MOB,API). - Make a project private (invite only) or public to the workspace.
- Turn features on and off per project: Cycles, Modules, Views, Pages, Intake.
- Define your own states and labels.
- Add members and set per-project roles.
- Archive a project when it's finished, without deleting anything.
Getting started
Create a project
- Click Projects in the left sidebar, then the create button. (Anywhere in the app: press N then P.)
- Fill in the form:
- Name — what the team calls it.
- Project ID — the prefix on every work item ID in this project. It's auto-derived from the name and you can override it. Letters and numbers only, up to 10 characters, always uppercase.
- Description — optional.
- Access — Private (accessible only by invite) or Public (anyone in the workspace except guests can join).
- Lead — optional, an owner for the project.
- Cover image and an emoji or icon — cosmetic, but they make the sidebar scannable.
- Create it. A second step appears where you choose which features the project uses. Everything can be changed later — except the project ID.
- Click Open project.
📷 Screenshot: the create-project dialog with the name, auto-filled project ID, access dropdown and lead.
About the project ID
The ID is the prefix in MOB-1, MOB-2. Those IDs appear in commits, chat
messages and conversations for years. It cannot be changed after the project
is created, so choose something short and unambiguous. Two projects in one
workspace can't share an ID.
Project settings
Open a project and go to Project settings. (Shortcut: G S from inside a project.) Settings are grouped into four sections:
General
- General — name, description, cover image, icon, access, lead. Also where you archive or delete the project.
- Members — who's on the project, and their role.
Features — one page per feature, each a single on/off toggle. Admin only.
- Cycles · Modules · Views · Pages · Intake
Work structure
- States · Labels · Estimates
Execution
- Automations
📷 Screenshot: the project settings sidebar showing the General / Features / Work structure / Execution groups.
Feature toggles
Each of the five project features is a switch in Project settings → Features → <feature>. Turning one off removes it from the project's sidebar and from the create menus; turning it back on restores it with your data intact.
| Feature | What it adds | Turn it off when |
|---|---|---|
| Cycles | Time-boxed sprints, burn-down charts | You don't work in sprints |
| Modules | Named deliverables with a lead and status | Your work has no long-running streams |
| Views | Saved filters + layout, shared with the project | Nobody's saving views |
| Pages | Rich documents inside the project | You keep docs elsewhere |
| Intake | An inbox of incoming items awaiting triage | You don't take external requests |
Only project admins can change these.
States
States are the stages a work item moves through — the columns on your board. Every project starts with five: Backlog, Todo, In Progress, Done and Cancelled.
Go to Project settings → States to add, rename, reorder, recolour or delete them.
Every state belongs to one of five state groups: backlog, unstarted, started, completed, cancelled. The group is what the product reasons about — cycle progress, burn-down charts and reports all count by group, not by state name. So when you add "In Review", put it in started; when you add "Won't Fix", put it in cancelled. Get the group right and everything downstream is right.
Work items in completed or cancelled states are the ones you're allowed to archive.
📷 Screenshot: Project settings → States, showing states grouped under Backlog / Unstarted / Started / Completed / Cancelled.
Labels
Labels are free-form tags — bug, frontend, tech-debt,
customer-request. They're defined per project in Project settings →
Labels, where you can create them, give them a colour, and group them.
A work item can carry any number of labels, and you can filter and group by them in every layout.
Use states for where the work is and labels for what the work is about. If you find yourself creating a state called "Needs design", it's probably a label.
Members and roles
Project settings → Members lists everyone on the project and lets admins add more from the workspace's members. To get someone into the workspace in the first place, invite them at Workspace settings → Members.
Three roles:
- Admin — full control of the project, including settings, features, states and deletion.
- Member — the working role. Creates and edits work items, cycles, modules, views and pages.
- Guest — restricted access, for contractors and outside collaborators. Guests cannot join public projects on their own.
The same page also sets member defaults for the project.
Tips
- One project per team or product, not per feature. Features are what Modules are for. Projects are expensive to split later, because a work item can't move… actually it can, but its ID changes, and people's links break.
- Public projects are discoverable. If you want a project people can find and join without an invite, make it public — that's the difference between the two access levels.
- Star a project (from the projects list) to pin it to the top of your sidebar.
- Archive rather than delete. Archived projects keep their history and can be restored; deleting is permanent.
Limits & good to know
- The project ID is permanent. There is no rename.
- Turning off a feature hides it, it doesn't delete anything. Your cycles are still there when you turn Cycles back on.
- Deleting a state requires moving its work items to another state first.
- Only project admins can change features, states and project-level settings. Members can create and edit work; guests are restricted further.