Creating a project
A project is where one body of conversations and its analysis lives - the conversations you collect, the portal people record through, and the chat, library, and reports built from them. Make one per question or event: “Spring budget consultation,” “Q3 user interviews,” “Team retro - June.” If you want two very different summaries out of one project, that’s a sign it should be two.
You need to be a workspace owner, admin, or member to create a project. (A workspace is the container for your people, billing, and projects; a project lives inside it. One workspace, many projects - more in organisations & workspaces.)
The create steps#
The wizard is three short steps:
- Name & context - give it a clear name and a paragraph of context (see the tips below).
- Access - open to your workspace (the default; everyone in the workspace can find it) or private (restricted even within the workspace). Private needs an Innovator workspace or above; on Free, projects are open.
- Review - confirm and create. You land on the project home, ready to set up the portal and start collecting.
The settings that matter#
You can change all of these later under settings → overview.
Name is dashboard-only - participants never see it, so name it for your own clarity.
Context is where the work pays off. Describe the project as you would to a sincerely interested, curious friend: your goal, the sessions, the questions you’re chasing, anything unique about it. Include place names, locations, and common abbreviations. The richer the context, the better the summaries and reports.
Language must match what people will actually speak.
Important
If a Dutch conversation is set to English, it gets transcribed as English. Pick the spoken language. Transcription is multilingual and handles code-switching, but the primary language has to be right.
Participant name is what dembrane calls the people who record - “participant,” “resident,” “student,” “member.” It shows in the portal and your conversation lists, so pick the word your audience recognises.
Conversation toggle controls whether new conversations can be added - use it to close a project to new input once a session is over, while keeping everything readable.
You can also move the project to another workspace (handy if you created it in the wrong place) and delete it.
Warning
Deleting a project is permanent and takes its conversations with it. If you only want to stop new input, use the conversation toggle instead.
A sensible first setup#
- Name it after the event, add a rich paragraph of context.
- Leave it open to your workspace.
- Set language to your room’s spoken language.
- Set participant name to whatever your audience calls themselves.
- Head to the portal editor for title, description, finish message, and key terms.
- Share the QR or link.
Related#
- Projects - the canonical feature reference.
- Setting up the portal - configure what participants see.
- Collecting conversations - every way to gather input.
- Organisations & workspaces - the containers above projects.
- Tiers & billing - what’s gated where.
Comments