Plane
Question about onboarding gating before first task interaction #8850
-
|
Hi, I was reviewing the onboarding flow and noticed that authenticated users are redirected to This effectively blocks access to the workspace and prevents any immediate interaction with issues or tasks. Was this flow intentionally designed to require full onboarding before allowing first task interaction? Curious about your thinking. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
|
You can actually skip the onboarding after entering your name and credentials. It's not required to complete all the steps before accessing your workspace. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for clarifying that — and you're right, the skip button is there.
What I was pointing at is slightly different: role and use case are
skippable, but the workspace step isn't — users can't reach any
authenticated route until isUserOnboard is satisfied. That's the actual
gate. The skip exists inside the wizard, not around it. Curious if that
distinction shows up in your drop-off data at all.
Le ven. 10 avr. 2026 à 15:44, Dancia ***@***.***> a écrit :
… You can actually skip the onboarding after entering your name and
credentials. It's not required to complete all the steps before accessing
your workspace.
Screenshot.2026-04-10.at.8.12.56.PM.png (view on web)
<https://github.com/user-attachments/assets/a77d84c6-5a72-440e-b8e3-c390a7c4af32>
—
Reply to this email directly, view it on GitHub
<#8850 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CANBVWT25UZSQJS2LXGAIPL4VECFZAVCNFSM6AAAAACXMG4BWKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJRHEYTMMQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Good observation, but here's the thinking. If you're a new user creating a Plane account, you need at least one workspace to do anything. Otherwise you'd land on a blank account with nowhere to create projects. That's the one required step. |
Beta Was this translation helpful? Give feedback.
-
|
Fair enough — makes sense as a deliberate gate for new accounts.
For what it's worth, I ran a broader analysis on Plane's onboarding and
billing flows as part of a codebase review I've been doing across
open-source SaaS tools. Found a few patterns worth flagging beyond this one.
If it's useful to the team, happy to share the full report directly with
whoever owns growth/product. No ask, just the findings.
Le lun. 13 avr. 2026 à 16:54, Dancia ***@***.***> a écrit :
… Good observation, but here's the thinking. If you're a new user creating a
Plane account, you need at least one workspace to do anything. Otherwise
you'd land on a blank account with nowhere to create projects. That's the
one required step.
If you're invited to an existing workspace, you skip the workspace
creation entirely and go straight to the workspace you were invited to.
—
Reply to this email directly, view it on GitHub
<#8850 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/CANBVWUU6CSJZPN5VHESDZL4VUESPAVCNFSM6AAAAACXMG4BWKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNJUGYZDKNA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Sure, you can send them over to support@plane.so. |
Beta Was this translation helpful? Give feedback.
Good observation, but here's the thinking. If you're a new user creating a Plane account, you need at least one workspace to do anything. Otherwise you'd land on a blank account with nowhere to create projects. That's the one required step.
If you're invited to an existing workspace, you skip the workspace creation entirely and go straight to the workspace you were invited to.