69 extensions. One framework.
Generic work tools ask every trade to bend around the same board. Noots does the opposite: an extension adds a tab to a project, changes a screen you already use, runs a job in the background, or opens a whole new area — installed, configured, scoped and governed per workspace.
Four shapes, one contract.
An extension declares what it adds and where it lands. The product renders it only through those named slots — which is why one can change how your workspace behaves without a line of it touching a core screen.
It adds a tab to a project
A new tab on the board's own strip, sitting beside Overview, Timeline and Meetings as though it had always been there — and removable from the strip whenever it stops earning its place.
- Billing — the client invoice for this project
- Site Work — the tab a crew uses with no signal
- RFIs — a numbered register per project
- Canvas — a freeform page pinned to the work
It changes a screen you already use
The more interesting shape, and the one the industry extensions are built on: they augment the screens you were already looking at rather than adding another destination to remember.
- A live countdown chip on a board card
- A billable-time panel inside the task detail
- A rule that makes the Gantt enforce finish-to-start
- A redaction pass over meeting text, and a shift roster the availability checker obeys
It runs in the background
Work that happens whether or not anybody has the tab open — and that genuinely stops the second you disable it, because the job checks the install state on the server before it does anything.
- SLA escalation that pages the next name up
- Monitoring alerts becoming SLA-clocked tickets
- An offline queue reconciling when signal returns
- A dependency ripple moving what a slip moved
It opens a whole area
The rest of the catalogue: self-contained areas that live behind a tile in the apps launcher, hidden until somebody adds them so the launcher is never pre-filled with things nobody uses.
- Codex, the workspace handbook
- Policy Library, Learning Hub, Decision Log
- Roadmap, Goals & OKRs, Standups
- Intake, Checklists & SOPs, Announcements
Worth being precise about: not one of the twelve extensions built for a specific industry is another app to open. They are tabs, chips, panels, rules and jobs inside the product you already have. The areas in the launcher are the rest of the catalogue.
An admin switch that is actually a switch.
Turning an extension off is not hiding a button. Every action, route, webhook and scheduled job it owns runs through one gate — session, organisation, permission, installed, enabled, plan-allowed — before anything happens. Disable a published board and its public URL stops answering that second.
Install
From the marketplace, or from the list your industry puts in front of you when the workspace is created. Owners, admins and managers only.
Enable & disable
A different thing from installing. Disabling takes the surfaces away and stops the jobs, and keeps every row the extension has already written.
Configure
SLA tiers, invoice rates, shift patterns, RFI approval chains, alert field maps — all in Org settings, rendered from the manifest's own schema.
Scope
An install belongs to the organisation; scope rows narrow it to a division or to a single team. No scope rows means everyone.
Govern
Every action, route, webhook and scheduled job re-checks the session, the organisation, the permission, the install state and the plan before it does anything.
Uninstall
Take it out of the workspace whenever the shape of the company changes.
Bundled by trade, installable on their own.
Say what you do when you create the workspace and the list in front of you is the one that fits — the tightest few already ticked, the rest offered, nothing installed that you did not agree to. The same choice decides your starter projects and the default tabs on every board.
Between 12 and 16 extensions fit a given trade, and between 4 and 8 of them are switched on at setup. A setup screen that installs fifteen things is a screen nobody reads.
There is a marketplace behind all of this.
Every extension is listed in the in-app marketplace alongside the rest of the catalogue — the CRM, the connectors, the board importer and the starter templates. Browse by trade or by category, install in one click, and submit your own app for review.
General Purpose
Pick General Purpose at setup and nothing industry-specific is installed. You get the core — projects and boards, meetings, the organization directory, mail, chat and calls, and the calendar — plus four workspace apps a new team of any kind reaches for in its first month. Everything else is one click away in the marketplace, and you can change your industry from Org settings whenever the shape of the company changes.
How the system behaves.
Every answer here describes what the framework does today, not what it is meant to do.
What is an extension, exactly?
What happens when I choose my industry?
What is the difference between disabling and uninstalling?
Can an extension be limited to one team?
Who is allowed to install one?
Do extensions get in the way of the base product?
Can we write our own?
What we don't claim
- There is no public extension SDK. Every extension in the catalogue is built by us, and Noots does not run third-party code inside your workspace.
- Submitting an app to the marketplace submits a listing to our review queue. It is a listing, not a deployment.
- No star ratings, review scores or install counts. Ratings were removed rather than corrected — the average a workspace saw was an average of itself.
- Some extensions need a paid plan, and the catalogue says which before you install rather than after.
- Changing your trade later changes what is offered and what new projects default to. It does not rebuild work you have already done.
- An extension is scoped to the organisation, a division or a team. There is no per-project install.