A Noot's tabs
The tabs every Noot has, the ones you can add, and how to add or remove them.
Every Noot opens with a strip of tabs. Three of them can never be removed; the rest are a default set you can rearrange — add what the project needs, take off what it doesn't.
The three that can't be removed
| Tab | What it's for |
|---|---|
| Overview | Counters, a status donut and "About this Noot". |
| Board | The kanban. Drag cards between and within columns. |
| Members | Who's on it — teams, their objectives, and any AI teammates. |
The rest of the default strip
A new project opens with seven more on top of those three — List, Timeline, Files, Meetings, Calendar, Capacity and Budget. Every one of them can be taken off, and put back later. Which seven you get depends on your industry and on your workspace's own override — see Industries & onboarding.
Tabs you can add
Use the dashed + at the end of the tab strip. The menu only offers what isn't already there — including anything you removed earlier — and once you've added everything it says so.
| Tab | What it's for |
|---|---|
| Backlog | The grooming queue — unstarted, undated work with the three grooming decisions inline. |
| Gantt | What depends on what: finish-to-start arrows and the longest dependent chain. |
| Starred | Just the work you've starred. It isn't on by default, because starring is already a board sort *and* a board filter. |
| Autopilot | Autopilot's plan, its management cycles and everything it changed. |
| Automations | "When this happens, do that" — this project's own rules, plus the workspace rules that apply to it. See Automations. |
| Keys | API keys and credentials for this project, behind a code. See The Keys vault. |
| RAID | Risks, Assumptions, Issues, Dependencies, Change requests, Stakeholders. |
| Goals | The org goals this project advances, with its real contribution. |
| Deployments | Releases, and the commits and pull requests against this project's tasks. |
Installed extensions can add tabs too — Canvas, Billing, Field and RFIs all arrive that way, and they come off the strip like any other tab. Hiding an extension's tab does not uninstall the extension, and the + menu can put it back. See What extensions are.
Rearranging the strip
- Reorder by dragging a tab, or by focusing one and pressing Ctrl (⌘ on a Mac) + ← / →.
- Remove with the × on the tab. Removal is confirmed, and the dialog says what happens to the data.
- The order and the removals are saved on the project, so everybody on it sees the same strip.
The strip is how a project is laid out for everyone on it, so adding, removing and reordering is limited to the person who created the Noot, its named leader, the lead of a team on it, a project manager, or an org admin. Everyone else sees the tabs and no controls. This is re-checked on the server, not just hidden.
What removing a tab does to the data
Most tabs are just a different view of the same tasks, so removing one takes nothing away. Five tabs own rows of their own, and for those the confirmation offers a real choice:
| Tab | If you ask it to remove the data |
|---|---|
| Budget | Deletes this project's budget and its expenses. |
| RAID | Deletes this project's RAID entries. |
| Automations | Deletes this project's own rules. Workspace-wide rules are untouched. |
| Keys | Wipes this project's stored credentials, its code and every live unlock. |
| Goals | Unlinks the goals rather than deleting them — a goal belongs to the organization and merely points at a project. |
For every other tab — List, Timeline, Gantt, Backlog, Capacity, Files, Calendar, Meetings, Deployments, Starred, Autopilot — removing it takes the tab off and nothing else. Add it back and everything is still there.