Sign In and Onboarding
Learn the initial dashboard flow for creating a workspace, selecting a project, and activating the first DecisionOps workflow.
Use this page when you are entering DecisionOps for the first time, returning to finish setup, or helping a teammate understand why they are still being routed through onboarding.
What You Need First
You need a supported sign-in method and access to the workspace you plan to use. DecisionOps currently supports GitHub sign-in and email magic link sign-in. If you are joining an existing workspace, you may also need an invite or an approval from an admin.
How Sign-In Works
Start at /login and choose either GitHub or email. After a successful sign-in, DecisionOps creates the browser session it needs for the dashboard and then routes you into the onboarding flow. New users usually begin at /start, while returning users are sent through /onboarding/resume so the app can determine the next required step.
How Onboarding Works
Onboarding has three major stages:
- Choose how you want to start on
/start - Create or select a workspace on
/onboarding/setup - Activate one value path on
/onboarding/value
The workspace step is where you create a workspace, use a personal workspace, pick an existing one, or request access. The same screen also lets you create, select, or defer a project. The value step is where you decide whether to start with a decision, connect a repository, or use DecisionOps in your IDE.
If you request access to an existing workspace instead of joining immediately, DecisionOps pauses onboarding on /onboarding/pending until that request is approved or denied.
What Success Looks Like
Onboarding ends after the first successful activation event. For example, creating a first decision, connecting a repository, or completing the first IDE authorization all count as activation. At that point, DecisionOps routes you to /decisions, and the main workspace becomes available.
Troubleshooting
If you expected to land in the app but keep returning to onboarding, the most common cause is incomplete setup state. Check whether the workspace selection, project selection, or activation step is still unfinished. If you are waiting on access approval, /onboarding/pending is the expected state until an admin responds.