[Due for payment 2026-04-23] [Due for payment 2026-04-20] Home - Getting Started tasks open not here page when default workspace is invited workspace

[jponikarchuk]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.58-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #86663
Email or phone of affected tester (no customers): sjdiosjondoidosd@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Search

Action Performed:

Precondition:

• User has completed onboarding with Manage my team's expenses intent.
• User is invited to another workspace.

1. Go to staging.new.expensify.com
2. Go to Workspaces tab.
3. Click 3-dot button on the invited workspace.
4. Click Set as default workspace.
5. Go to Home.
6. Click any task except Create a workspace.

Expected Result:

"Getting started" section should be hidden when default workspace is invited workspace.

Actual Result:

"Getting started" section is shown when default workspace is invited workspace.
Any task except Create a workspace opens not here page.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Video.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @ZhenjaHorbach

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #86663

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[MelvinBot]

Proposal

What is the root cause of that problem?

The useGettingStartedItems hook (useGettingStartedItems.ts:43) uses NVP_ACTIVE_POLICY_ID to determine which workspace to build the checklist around. This is the same Onyx key that gets updated when the user sets any workspace as their default (via "Set as default workspace").

The visibility guards (lines 52–63) only check that the intent is MANAGE_TEAM, the policy exists and is a paid group policy, and the trial is within 60 days. There is no check that the user is an admin/owner of that policy. So when the user switches their default to an invited workspace, all checklist routes (workspace overview, accounting, categories, company cards, rules) point to admin-only pages on the invited workspace — pages the user can't access, resulting in "not here" errors.

What changes do you think we should make in order to solve the problem?

Add a policy role check to the visibility guards in useGettingStartedItems. The section should only be shown when the user has admin (or higher) access on the active policy. Concretely, add a guard like:

if (policy.role !== CONST.POLICY.ROLE.ADMIN) {
    return emptyResult;
}

This ensures the Getting Started section is hidden when the default workspace is one where the user is just an employee/auditor, since the checklist items all require admin access.

What alternative solutions did you explore? (Optional)

An alternative would be to store the original onboarding policyID separately (e.g. in a dedicated Onyx key) and always use that for the Getting Started section, ignoring NVP_ACTIVE_POLICY_ID. This would keep the section tied to the workspace the user created during onboarding. However, the admin role check is simpler and also correctly handles edge cases where the user loses admin access to their own workspace.

Supporting evidence

• activePolicyID is read at useGettingStartedItems.ts:43 and used for all route construction (lines 70–113)
• "Set as default workspace" updates NVP_ACTIVE_POLICY_ID at SetDefaultWorkspacePage.tsx:52 and WorkspacesListPage.tsx:405
• The enableFeature callbacks also use activePolicyID, meaning they would attempt to modify settings on the invited workspace — which would fail if the user isn't an admin

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[OSBotify]

Investigation Summary: Classification is Frontend bug. Causing PR is 86663 by @adamgrzybowski (High confidence). Recommendation: REVERT. PR 86663 introduced the Getting started section without checking whether the user is an admin or owner of the active policy. When a user sets an invited workspace as their default, the section incorrectly appears and all task links navigate to workspace-admin routes that non-admin members cannot access, producing the not-here page. Assigned: @adamgrzybowski (PR author), @ZhenjaHorbach (approving reviewer), @JmillsExpensify (approving reviewer), @mountiny (approving reviewer). Labels: DeployBlockerCash kept - this is a Frontend bug in Expensify/App, no label changes made. Root cause: In src/pages/home/GettingStartedSection/hooks/useGettingStartedItems.ts the visibility guard at line 57 checks isPaidGroupPolicy() (policy type only) but does NOT check the user role. It passes for any TEAM or CORPORATE policy regardless of whether the user is an admin, owner, or invited member. The isPolicyAdmin() utility exists in src/libs/PolicyUtils.ts and should have been used to guard this section.

[ZhenjaHorbach]

@MelvinBot implement this