Help center

The access log records who read personal records, where in the service, and why. Edits are already in the audit log; the access log covers reads: contacts, interactions, expenses, data-request exports and other records about people.

Connect your organization's ledger in QuickBooks Online or Xero so Treasury can compare each budget with what your books say was actually spent. The connection is read-only: the chart of accounts and your spending transactions come in; nothing is ever written to the ledger, and nothing here creates, approves or pays a bill. There is no payment or bill-pay access at all.

The Admin page is where owners run the workspace: who has which role, what has changed, exports, usage, and the settings that other parts of the app add. It appears in the main navigation for owners only. Anyone else who opens it is told to ask an owner.

AI reads your documents and proposes what it finds in them, such as meetings, deadlines, decisions and the members of a public body. It never changes your data on its own: each proposal waits for a person on your team to approve or reject it.

Some treasury records need someone other than their author to sign them off: budget lines always do, and expenses do above a threshold. Approvals are signed records. Each signature stores who signed, with which roles, when, and a fingerprint (a sha256 hash) of exactly what they saw. A signature cannot be edited or deleted afterwards, not even by an owner.

On the Enterprise plan, owners download the audit log from Enterprise → Audit log export for a security monitoring system (SIEM), a records request or an auditor.

On the Enterprise plan, owners set up scheduled exports of the organization's data to the organization's own S3-compatible bucket (AWS S3, Cloudflare R2, MinIO, Google Cloud Storage interoperability). Each dataset's shape is published as a JSON Schema: the data contract.

Publish your organization's meetings and rituals to a Google Calendar or Microsoft 365 calendar, so they sit beside everything else in people's calendars. Owners set it up under Initiatives → Integrations → Calendars.

In a research note, a citation binds a statement to one or more excerpts: exact passages of source documents (see Sources, "Excerpts"). A citation names excerpts by their ID, never by a URL or a pasted quote, so it always leads back to the verbatim text, its page, and the document's provenance.

An owner can ask the platform team to close an organization. Closing ends everyone's access to it. You can also close your personal workspace, as part of deleting your account.

The conflict register records three things:

The platform monitors a place's public sources through coverage packs. A coverage pack covers one place (a city, a county, a national legislature). It holds the connectors for that place (small programs that each read one official source on a schedule), saved test cases that show the connectors read the source correctly, and a survey of each source's terms. This page explains how a member asks for a place, and how the people who run the platform turn a request into monitored coverage. What the coverage banner's statuses mean is in Sources, "Coverage".

A data request (a data-subject request) is a person asking what the workspace holds about them, or asking for it to be erased. Owners handle requests under Trust → Data requests (/trust/data-requests). Any member can make a request about themselves under Trust → Your data and account (/trust/your-data): see Asking for your own data.

Every initiative keeps a decision log: what was decided, why, by whom and when. Later readers can see how the initiative got where it is, and the organization can learn from it.

The Decision Monitor follows what the bodies serving a place are deciding: their meetings with each agenda item, and the matters (bills, ordinances, resolutions, rules, notices, contracts, appointments) that move through those agendas.

An Enterprise organization can run on a deployment of its own: its own copy of the service, with its own database, cache, file storage and sign-in system, serving only that organization. It runs the same software as the shared service, in single-tenant mode: one organization per deployment.

The Doctrine Engine holds your organization's positions: what it stands for on a topic, why, and on which claims and principles that rests. Every change is a new numbered revision; a position is approved by someone other than the person who wrote it before it is published, and its whole history can be replayed from the record.

Is the place you work on, or a public source you need, not covered yet? Ask for early access. We work with early-access organizations to add their place and their sources. Enterprise plans are arranged the same way, and the same form takes questions about plans.

Initiatives → Execution dashboard shows whether the work is moving. It covers every initiative you can see. Restricted initiatives count only for the people who can see them.

You can take a complete copy of your workspace at any time: every record, the audit trail and the files your records point to, in one ZIP archive of plain JSON and original files. Every plan includes it. A plan limit never blocks an export, so your data is never held hostage.

Setup walks a new workspace through five steps. Each step is ticked when the thing it asks for exists, so you can leave and come back: the list picks up where you are. Owners find Setup in the main navigation, and the workspace home shows Continue setup with the next step until it is done.

Governance holds the organization's committees, their meetings and votes, and its policies. Every outcome (a resolved agenda item, a closed vote, an adopted policy) is written to the decision log, so the record of who decided what, and why, is in one place.

The Ideology Mapper is a map of what your organization argues: the claims it makes, the principles it argues from, and how they bear on one another (argument edges). Every factual claim says how it is supported, by an exact excerpt of a source document, or it is visibly unsupported. AI can suggest claims and edges; nothing it suggests counts until a person accepts it.

Impact Analytics shows how your published work reaches people and how well it is sourced, as aggregate numbers with their definitions beside them. It never identifies a reader.

An information barrier keeps restricted projects away from the members on the other side of it. Its typical use is a member who holds a public office and must not see the organization's strategy on matters that office decides.

An initiative is a piece of work your organization commits to, such as applying for a vacancy, passing a resolution or running a petition drive. Every initiative has:

The Institution Map shows the public bodies that serve a place: the federal, state, county and city governments, their boards, commissions, committees and agencies, how they fit together, what each is charged with, and who holds its seats. Every body answers the question "What level of government is this?", and every fact links to the official document it was read from.

Institutional memory keeps how your organization does things and what it has learned, so the work does not depend on one person. It holds:

An issue is something your workspace is following, such as a proposed rule, a ballot measure or a budget cut. Issues are the hub of the workspace:

A location is a place your workspace follows: a city, a county, a state or province, or a country. It is saved together with its jurisdiction stack. A jurisdiction is a government or a district with authority over the place. The stack lists every one that applies, from the place's own city council up to the nation. Work in other parts of the app can be filtered by a location, and the location menu in the header sets the location you are looking at.

A task can name the skills it needs. Matches on the task suggests people and shared resources that offer those skills, with the reasons, so someone can ask them. A match is only ever a suggestion: nothing is assigned until the person asked says yes.

Movement Hub keeps your organization's members, its educational events and its research collaborators, each resting on the consent the person gave. It records who agreed to what, sends only the transactional emails a person signed up for, and treats dues as a link to your own payment page: nothing about payments is processed or stored.

Initiatives → My work gathers what is yours across every initiative you can see:

Narrative Radar finds the themes running through a set of documents week by week, and always says how lopsided the sources behind them are. Each theme drills down to the documents and passages it comes from, and who published them. It is about documents and publishers, never about people.

The network shows how the records in your workspace connect through their links: issues, initiatives, research notes, institutions, opportunities and the other records you have linked. Open it from Analytics → Network.

Notifications tell you when something in your workspace needs your attention: a role you were given, an export that is ready, a change to an issue you opened. The bell in the header shows how many are unread.

Onboarding gives each new member a short checklist for their first weeks, and lets project leads see how far everyone has got. The setup wizard installs a starter checklist; see Getting started. Your open checklist also shows on the workspace home: its next three items, each a link to where it is done, and a link to the whole checklist.

The Opportunity Radar lists the ways people in a place can take part in public decisions: comment periods, hearings that take testimony, board and commission vacancies, grants, procurements and surveys. Each shows whether it is open, its deadline in the place's own time, who may take part and how, all as the official source states them.

The participation log is your workspace's record of what people did through official channels (attended a meeting, submitted a public comment, testified, applied for a seat, asked a question) and what came of it. The watchlist is what the workspace follows. Both come with the Opportunity Radar and belong to the workspace only.

The pilot-metrics page puts the platform's pilot targets beside your workspace's own usage and delivery measures. Open it from Analytics → Pilot metrics. Every member can see it.

Billing shows your organization's plan, its trial or billing period, and how much of each limit you are using. Every member can see it; only owners change the plan. Owners reach it from the main navigation.

A portfolio groups initiatives for a period, with the hours a week the organization can put into them and a budget envelope. Scenarios on a portfolio ask "what if": different dates, budgets, hours, or which initiatives to include. Nothing here changes the initiatives themselves.

A procedure writes down how a recurring piece of work is done, such as the monthly bank reconciliation or booking the library's meeting room, so that someone other than the person who usually does it can do it. Procedures live in the library.

Execution → Programs compares programs: how much work they get done, how many of their commitments they keep, how long work takes, and how their spending tracks the plan. It sits alongside the Execution Dashboard.

A project groups the issues and work for one campaign, programme or question, such as a shoreline campaign or a levy renewal. Projects keep a busy workspace navigable, and they let you give someone a role in one project without giving it to them everywhere.

This page is for the developers who connect your organization's own tools to the workspace. On the Enterprise plan, an owner creates API keys on the Enterprise page. A key lets a program read your organization's workspace in two ways: through a REST API, for your own tools and data warehouse, and through an MCP server (Model Context Protocol), which connects AI assistants. A key can only read: nothing reachable with a key can change anything.

The public graph is a download of the public record for one jurisdiction (one government, such as a county or a city): its public institutions, the public roles in them and the relations between institutions, as open files. Open it from Analytics → Public graph and choose a jurisdiction. Anyone can download it; it needs no workspace.

Publishing puts an approved document or position on a public page that anyone can read without an account: the text with every citation, the sources it cites, who wrote, approved and published it, and a changelog. A published version never changes. A correction is a new version at the same link, with a note saying what it corrects; a withdrawal takes the page down and keeps the record.

The service limits how many requests it accepts in a short time, so one busy script or one workspace cannot slow everyone else down. Ordinary use stays far below the limits. When a limit is reached, the app shows Too many requests. Wait a moment and try again. A script that uses the API gets a "Too Many Requests" answer that says when to try again.

The Relationship Directory keeps the people your organization works with, only with their consent, and the meetings, calls and hearings you have had with public bodies and officials.

A research note is a piece of cited writing about an issue: what a proposal changes, what a hearing decided, what the record does and does not show. Every statement in a note is either cited to an exact excerpt of a source document or visibly marked unsupported. A note is reviewed by someone other than its author before it is shared, and its PDF export carries a record of how it was made.

The resource network lists what your members and partners are willing to share: skills (such as GIS mapping or Spanish translation), tools (a projector, a van), facilities (a meeting room) and what partnerships offer. Members can see when each resource is available and ask to use it.

Retention policies say how long the workspace keeps each kind of personal record. Every night, records older than their policy are deleted or anonymized.

Rituals are the organization's recurring meetings, each with an agenda drawn from what is actually happening. Rituals lists the five, when each is next due, and which are not set up yet.

The search box in the header looks through your workspace. Type a few words and press Enter. Results are grouped by kind of record (for example Issue, Project or Initiative), with the best matches first in each group and the matching words highlighted.

On the Enterprise plan, owners connect the organization's identity provider (IdP) on the Enterprise page (main navigation, owners only). Members then sign in through the IdP with SAML 2.0 or OpenID Connect, and the IdP can create, update and remove members through directory sync (SCIM 2.0).

Post your organization's progress to one Slack channel: milestones completed, decisions logged, rituals coming due and adjourned, votes, policies and more, and a weekly digest. Owners set it up under Initiatives → Integrations → Slack.

Every fact, quote and briefing in the platform points back to a source document: a page, PDF or file that was fetched or uploaded, stored exactly as received, and kept with a record of where it came from. This page explains what that record holds, how to upload your own documents, how excerpts work, and what the coverage banner tells you.

Initiatives → Team lists everyone in the organization and the roles they hold, with the number of people the plan allows. Every member can see the list. Only owners see email addresses.

The document viewer is where research starts: read a source's text, save the passages that matter as excerpts, and put them to use in a research note or as evidence for an issue. It is part of the Evidence & Content Studio, and opens from a note's evidence ("Open in the document") or from a link to one excerpt, which scrolls to that excerpt and focuses it.

The studio is where research notes grow into the documents an organization puts its name to: briefs, reports, testimony or public comments and one-pagers, as well as research notes themselves. Every one of them is written in the same editor, cited the same way and reviewed the same way as a research note. The studio adds templates, comments, suggested edits, writing together, a citation-support check before review, more export formats and publishing.

Treasury keeps your organization's money records: budgets, the lines they are planned in, the expenses you have recorded, a monthly cash plan and how actual spending compares with the plan. It never holds, moves or pays money. There are no bank accounts, card numbers or payment buttons. You pay through your bank or payment processor as usual, then record what you paid here.

This page is for the developers who build your organization's own systems. A webhook tells your system at once when something changes in the workspace, for example when a project is created. On the Enterprise plan, an owner registers webhook endpoints (addresses on your own server) on the Enterprise page. Each event you subscribe to is sent to your endpoint as a signed JSON message, and sent again until your endpoint accepts it.

The weekly briefing is a short, personal summary for one place: what changed in the public record last week, deadlines coming up, what waits for your review, and outcomes your workspace recorded. It is built the same way every time from the same facts, so two people with the same place and week read the same briefing.

Your progress review is your own record of taking part in public decisions and building your organization, month by month. Open it from Analytics → Your progress.