Your Missions
Focused, shared spaces scoped to a single thread of work — with their own Files and Artifacts.
What are Missions
A Mission is a focused, shared space scoped to a single thread of work — think of it like a project folder. Your Workspace is already collaborative on its own; a Mission lets you go a layer deeper, giving one specific effort its own home so the outputs and files that belong to it don't get scattered across conversations.
A Mission scopes two things:
- Artifacts — saved reports, summaries, and other outputs produced for that thread of work.
- Files — files relevant to that thread of work.
Both behave the same way: everything scoped to a Mission still exists at the Workspace level too. The Mission's own Files and Artifacts views show just what's scoped there; the Workspace-level Files and Artifacts pages show everything, mission-scoped or not.
A Mission doesn't hold records — People, Organizations, and Events live at the Workspace level regardless of what Mission you're working in. A Mission scopes work and files, not the network itself.
Creating and managing a Mission
Note: creating and deleting a Mission are Admin-only actions. Every user can view, work within, and save to any Mission that exists.
Create a Mission
You can create a Mission two ways:
- Find / Create in the sidebar (⌘K) → Create → Mission.
- From the Missions index page, using Create in the top right.
When you create a Mission, add a description — this is how you give the Mission its context: what the thread of work actually is, so anyone opening it understands its scope.
Delete a Mission
From the Mission's own page, open the kebab menu (top right) and choose Delete.
Deleting a Mission removes the Mission itself, but not what's inside it — Artifacts and context files move up to exist at the Workspace level and need to be deleted separately.