Skip to content

Don't show the classic welcome tour on the Expert home - #9023

Draft
cstns wants to merge 1 commit into
mainfrom
8938-no-classic-tour-on-expert-home
Draft

cstns wants to merge 1 commit into
mainfrom
8938-no-classic-tour-on-expert-home

Conversation

@cstns

@cstns cstns commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

Closes #8938

A new user whose team has the Expert lands on the Expert home after verifying their email, and the "Welcome to FlowFuse" tour started right there. The tour and the getting started modal were written for the classic dashboard (hosted instances, remote instances, recent activity), none of which is on the Expert home, so it pointed at things that aren't there.

The team page now decides: when AI onboarding or the Expert is on, it withdraws the queued tour instead of starting it, and still wakes the assistant if it should. The email verification page used to make that call itself, but no team is loaded for an unverified user yet, so it now always queues the tour and leaves it to the team page. The Welcome Tour entry in the user menu is hidden on the Expert home for the same reason. The AI connector dialog also waits until AI onboarding is done, so it doesn't pop up over it, but only on teams that actually get AI onboarding, since every new user starts in the onboarding stage.

Covered by new tests for the team page and the page header, and the email verification spec is updated for the simpler flow.

The welcome tour and the getting started modal walk the classic dashboard, which the Expert home doesn't have. The team page now withdraws the tour when AI onboarding or the Expert is on, the Welcome Tour menu entry is hidden on the Expert home, and the AI connector dialog waits until AI onboarding is done. The email verification page always queues the tour and leaves the decision to the team page, since no team is loaded for an unverified user.

Closes #8938
@cstns cstns added this to the 3.2 milestone Oct 23, 2026
@cstns cstns self-assigned this Oct 23, 2026
@cstns cstns modified the milestones: 3.2, 3.3 Oct 23, 2026
@codecov

codecov Bot commented Oct 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.54%. Comparing base (23079bb) to head (802d4d1).
⚠️ Report is 6 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #9023      +/-   ##
==========================================
+ Coverage   79.46%   79.54%   +0.08%     
==========================================
  Files         475      475              
  Lines       26018    26076      +58     
  Branches     6934     6950      +16     
==========================================
+ Hits        20674    20741      +67     
+ Misses       5344     5335       -9     
Flag Coverage Δ
backend 79.54% <ø> (+0.08%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

This branch was successfully deployed

1 active deployment
staging — 802d4d1a Deployed Oct 23, 2026 by cstns via Deploy application #12694
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New users get the classic welcome tour on the Expert home

1 participant