Projects
A project groups the recordings and documents that belong together, for a client, a product, or a sprint, and becomes a scope you can question as one body of evidence.
- Updated
- 8 October 2026
- Read
- 3 min
- For
- Everyone
Four things a project does.
Projects are unlimited on every plan, so group as finely as is useful.
- Groups mixed evidence
- Recordings and documents together. A contract and the call where it was negotiated belong in the same place.
- Becomes a question scope
- Choose Ask project and the answer draws on everything inside it, citing spoken evidence by timestamp and written evidence by page.
- Shows its own totals
- Tiles count its recordings, documents, what is ready or processing, findings, and footage. Sources lists every item; the Artifacts tab counts findings by type.
- Can be reorganised
- Move recordings and documents between projects at any time without reprocessing anything. Edit renames the project or changes its kind and description.
Create one, file work into it, find it again
Create one
On Projects, choose New project. Give it a name, a kind (Discovery, UAT, Sales, Demo, Research, or Support), and an optional description.
Projects: each one with its recordings, findings, and last activity, plus the recordings not yet filed. File work into it
Choose the project when you upload, or move existing recordings and documents into it from their row menus. The Unfiled card on Projects collects recordings that are not in any project yet.
Find it again
Search Projects by name, client, or description, filter by Active or Processing, and sort by recent activity, name, recordings, or artifacts under More filters.
How teams tend to use them.
By client
Agencies keep one project per client, so a findings export or a question never crosses an account boundary.
By release
QA teams keep one per release or test cycle, which makes the sign-off packet a matter of exporting the project.
By research round
Product teams group a round of interviews, then ask the whole round rather than each session.
Access follows the workspace
Everyone in the workspace sees projects under their role. Projects organise work; they are not a permission boundary.
Roles decide what each member can do inside a project. See team and workspace.
Projects, answered.
As many as you want. Projects are not metered on any plan.
A recording belongs to one project at a time, and can be moved. That keeps a project total meaningful.
No. Everyone in the workspace can see the projects in it, under their role. Use a separate workspace when you need a hard boundary.
Every ready recording and document filed in it. Anything still processing joins the scope once it finishes.