A records request, packaged in one click.
Requests go into a register rather than somebody's inbox, and one click packages a project's full history as a real PDF and structured JSON with a checksum. A sanitised board on a public URL shows the citizen the fields you chose and nothing else. Inter-agency guests see the one programme they were invited to. Choose Government & Public Sector at setup and all three are queued.
7 apps queued at setup — untick any of them before you finishDefault project tabs
Goals and RAID are on, Capacity is off — public work is measured against published objectives.
Projects created on day one
- Programmes
- Public Records
- Procurement
The three that do the heavy lifting.
Choose this industry during setup and its tools are queued for you. Review the list, drop anything you don't want, and the workspace initialises with the rest already working — or install any one of them on its own, later, from the marketplace.
FOIA Exporter
A request register plus one-click packaging of a project's full history as a real PDF and structured JSON, carrying a content checksum.
- A register of requests, tracked as work
- One-click packaging of a project's full history
- A real PDF plus structured JSON
- A content checksum on the package
Public Read-Only Boards
A sanitised board on an anonymous public URL, with field-level control of exactly what is exposed and what is not.
- An anonymous public URL per board
- Field-level exposure control
- Internal chat and comments never leak
- Disable it and the public URL stops answering at once
Advanced RBAC
An inter-agency guest register with field-level view and edit rules, enforced on the server rather than by hiding a control.
- A register of inter-agency guests
- Field-level view and edit rules
- Enforced server-side on every request
- Guest scoping is per project
What changes, in the hours it actually changes.
Three moments from an ordinary week. Every one of them is a thing the product does, not a thing it could be configured to do one day.
09:15
a records request arrives
It goes into the FOIA register rather than someone's inbox. When it is time to respond, one click packages the project's full history as a real PDF plus structured JSON, with a content checksum so the recipient can prove the package they hold is the package you sent.
12:00
the public sees the programme, not the room
Public Read-Only Boards publishes a sanitised board to an anonymous URL with field-level control over what is exposed. Internal chat and internal comments are never part of it. Turn the extension off and the public URL stops answering immediately — the gate is on the server, not on a hidden button.
15:40
a contractor joins one project, not the agency
Advanced RBAC keeps an inter-agency guest register with field-level view and edit rules, enforced server-side rather than by hiding controls. A contractor invited to one programme sees that programme.
These sit on top of the whole product.
- Public meetings and committee sessions become owned action items automatically
- The Compliance Audit Logger is available here too — append-only, exportable
- Timelines and milestones that grade themselves from real progress
- SAML/SCIM single sign-on, two-factor authentication the workspace can require of every member, and an IP allowlist
- Private AI: run every AI feature against a model your own organisation operates
- Ten interface languages and a high-contrast palette
The honest edges.
- A FOIA package inlines meeting summaries and action items. It does not inline full transcripts.
- Advanced RBAC governs this extension's own surfaces and its guest register. It is not a field-level permission layer over every board in the product.
- Guest scoping is per project rather than per task.
- Noots holds no FedRAMP, StateRAMP or SOC 2 authorisation, and does not claim one.
The model can be one you run, and ours never sees the file.
Public bodies are the buyers most often told they may not send a record to a commercial AI service. So on the Business plan the address is yours to choose: give Noots an OpenAI-compatible endpoint your organisation operates and every AI call the product makes goes there — summarising a committee session, triaging correspondence, drafting a response, Autopilot, Hoot. Not a copy, and not a fallback.
What the control actually is
- One resolver decides where every model call goes, so switching the endpoint moves all of them at once — there is no surface that quietly kept using ours.
- A killswitch, on by default. If your server is unreachable the feature fails and names your server; nothing is retried against our provider, not during an outage and not if the plan lapses.
- The endpoint must be https and must resolve publicly. Noots re-checks the address on every call rather than only when it is saved, pins the one address it dials, and refuses redirects.
- The stored key is sealed with AES-256-GCM and never returned to a browser again — not even to the administrator who typed it.
- A five-check test runs before anything routes and again every day, on a fixed prompt that is never your content. One of the checks re-sends the request with no key, which is how a self-hosted model server turns out to be usable by anyone who finds the URL.
- Every call is recorded where your administrators can read it: when, which feature, which host, and whether it worked. Never what was in it.
Where the line actually is.
- It decides which model reads your text. It is not database-level encryption: the transcript and the summary are stored as ordinary text in our database either way, and we will not describe that as encrypted at rest.
- Noots never stores meeting audio, with or without it. There is no file storage in the product — audio is transcribed in flight and the recording is not kept.
- Bring your own transcription and those meetings come back as prose with no speaker labels, because the OpenAI-compatible audio API has no diarization and inventing speakers is something we refuse to do.
- A call captured by a third-party meeting bot arrives as a link rather than a file, so your own transcription endpoint cannot take it. It fails and says so rather than sending the recording elsewhere.
- One exception, and it is one you make: if you separately connect a third-party AI provider with your own key, work you push to it goes to that provider, because that is what you asked for.
- It is a Business-plan feature, configurable by an owner or an administrator only, and it is not an authorisation of any kind. Noots still holds no FedRAMP, StateRAMP or SOC 2.
How Government & Public Sector actually runs.
Each of these is a project in Noots — its own board, tab strip, meetings, calendar and members. They are not pre-built modules and we will not pretend they are: what the industry gives you is the right defaults around them.
Built for the way your trade actually runs.
The ones buyers ask first.
What is actually in a FOIA package?
Can the public see internal discussion on a public board?
How far does Advanced RBAC reach?
Do our records have to go to a commercial AI service?
Open a workspace that already knows Government & Public Sector.
Answer what your organisation does, review what gets installed, and start with the boards, meetings, chat and calendar already in the right shape.
Free to start · No credit card required