Projects

A project holds one body of work: the conversations that belong together, plus everything that grows out of them - transcripts, summaries, themes, chats and reports. You record into a project and analyse its conversations as a set. A good rule: one question or engagement per project. If you’d report on it as one thing, it’s one project.

Projects live inside a workspace, so what you can do depends on your workspace role. Members and up can create and edit; only owners and admins can delete, move, or make a project private. Creating a private project needs an Innovator workspace or above (see tiers & billing); everything else works on every tier.

Creating a project#

Open your workspace, go to Projects, choose New project, and fill in three short steps:

1. Name & context. The name is dashboard-only - participants never see it, and you can change it later. Context is the one that matters: describe the project as you would to a sincerely interested, curious friend - the goal, who’s in the room, what you want to learn, anything unique about it. Include place names, locations and common abbreviations. The language model reads this when it writes summaries and answers, so honest context means sharper analysis.
2. Access. Choose who in your workspace can see and work on the project. This sets its visibility. Private needs Innovator or above.
3. Review. A final check, then create. You land on the project home, ready to set up the portal and start recording.

Project settings#

Open a project and go to Settings.

• Name - rename at any time.
• Conversation language - the project default. Set it to what participants will actually speak: if a Dutch conversation is set to English, it gets transcribed as English. (Transcription is multilingual regardless - see transcription.)
• Visibility - open, invite-only, or private (see below).
• Conversation toggle - switch off the ability to start new conversations when an engagement closes. Existing conversations stay readable.
• Participant-name collection - whether the portal asks people for a name. Finer control lives in the portal editor.
• Move project - move it into another workspace (owners and admins). Handy for handing work between teams, or for partners moving between an internal and an external-client workspace.
• Delete project - permanent, and takes the conversations, transcripts and reports with it.

The portal editor, access and usage sections each have their own home: shaping the recording experience lives in the portal editor, and metered hours are explained in tiers & billing.

Visibility#

A project sits in one of three states, mirroring how workspaces handle visibility:

• Open - everyone in the workspace can see and (per their role) work on it. The simplest default for a team that trusts each other.
• Invite-only - visible to people who’ve been added, plus workspace admins.
• Private - visible only to people you give access, person by person, from Settings → Access. Admins aren’t auto-joined. Adding a colleague to a private project doesn’t change their workspace role; it just opens that one project to them. Needs Innovator or above.

Finding projects again#

The Projects view has three ways back: Home (your projects, most relevant first), Pinned (keep what you’re working on at the top), and Search (find one by name when the list grows).

Related#

• Organisations & workspaces - the container a project lives in.
• The portal editor - shape how people record for this project.
• Conversations & transcripts - what fills a project up.
• Roles & permissions and tiers & billing
  • who can do what, and what each plan unlocks.