Members, RAID, Goals, Budget & Deployments
What the less obvious project tabs actually hold.
Members
Who's on the project, grouped by team — each with its specialty, its objective on this project and a done/total progress chip — then anyone on the Noot outside a team, then any AI teammates. If the Noot is visible org-wide with no teams attached, it says so plainly rather than pretending to a roster it doesn't have.
RAID
Six registers, each as a pill tab with a live count: Risks, Assumptions, Issues, Dependencies, Change and Stakeholders. Each has its own fields — Risks carry impact, likelihood and a mitigation; Issues carry a severity and a resolution; Stakeholders carry influence, interest and an engagement plan.
A risk that names the task it threatens shows up as a risk signal on that task in the Timeline. Autopilot and the meeting pipeline write into these registers too, so a risk raised in a meeting lands here rather than in someone's notes.
Goals
The org goals this project advances, each with the Noot's real contribution (its own task completion, which is what actually moves the goal), plus status, owner and target date. Link and unlink in place.
Budget
One project's money: a budget figure with a period, spend measured inside that period, plus YTD and all-time. Breakdowns by task, by category and by person. You can attach receipts, and request more budget — approving a request genuinely raises the budget rather than just marking it approved.
Money mentioned in a meeting becomes a proposed expense that a person has to confirm. A transcript can never move a project's budget by itself.
Deployments
What this project has shipped: releases, and the commits and pull requests linked to its tasks with their state. It only shows the "connect GitHub" prompt when GitHub genuinely isn't connected. GitHub sync is on the Business plan and above.