Workspace

Workspace

Home overview screenshot

Screenshot

What This Page Solves

Workspace is how you keep different projects from collapsing into one giant list.

It is useful when you need to:

• separate clients, teams, or projects
• keep transcription and note history searchable
• reduce cross-project mistakes

When To Use It

Prefer Workspace when

• multiple projects run in parallel
• different teams or clients should not share one default library
• migration and archival matter over time

Do not wait too long to use it when

• the default workspace is already mixing unrelated work
• different projects need different naming or retention rules

Recommended Workflow

1. Create workspaces early, before the library becomes messy.
2. Use clear names and short descriptions.
3. Confirm the current workspace before each new transcription or AI session.
4. Archive or migrate completed work deliberately instead of letting everything stay active forever.

Key Decisions

1. Separate by project, not by mood

Avoid vague names like new, test, or misc. Prefer names people can search and understand later.

2. Keep workspace boundaries operational

Workspaces are not just visual folders. They reduce the chance of mixing notes, transcripts, and AI context across projects.

3. Treat migration carefully

Before moving assets, check:

• destination workspace
• quotas or policy limits
• whether key notes or exports should be backed up first

Common Mistakes And Troubleshooting

• Using vague workspace names Make them searchable and project-specific.
• Keeping all work in one default space Split earlier to reduce later migration cost.
• Migrating without checking the destination Confirm limits and ownership first.

Read Next

• Transcript review workflow: Note
• AI follow-up after review: AI Chat
• Core settings and defaults: Settings Overview