Set up your workspace

Goal

An account, a signed-in session, and a workspace you understand. Done means you know where you are, what belongs to the workspace, and what to do first.

Image: workspace home after first sign-in with empty states pointing at next actions.

Steps

1. Register for an account, or sign in if you already have one. Registration asks for the minimum needed to own a workspace — the product, not your infrastructure, holds accounts.
2. Land in your workspace. Everything you do — sources, workflows, ontology, skills, runs, feedback — belongs to exactly one workspace. When colleagues join the same workspace, they see the same state, history, and evidence you do.
3. Orient once before building:
   • Integrations: where data systems get connected. Empty now; it fills in with Connect data.
   • Pipeline Studio: where workflows get authored from requests. Empty now; it fills in with Run your first pipeline.
   • Runs and history: where executions and their evidence live. Empty until your first commit.
4. Decide the first question before touching configuration. A workspace set up around one real decision ("which accounts are at renewal risk?") beats a workspace connected to everything and aimed at nothing.
5. Do nothing else yet. No sources to configure here, no settings to tune — breadth comes after the first result, not before it.

What good looks like

• You can sign out and back in and land in the same workspace.
• You can state the workspace's first question in one sentence.
• Empty states read as invitations, not errors.

Next

• Connect data — the first real step.
• The full first-result flow: Getting started.