[Due for payment 2026-03-04] [$250] Sign up - Still assign guide for Track users after created workspace

[izarutskaya]

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.17-7
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from BrowserStack:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @danielrvidal
Slack conversation (hyperlinked to channel name): #expensify_convert

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Sign up with new account (without +)
3. Choose Track and budget expenses and finish the flow
4. Go to Workspace tab > create workspace > admins room

Expected Result:

Assign Track user created workspaces to Concierge.

Actual Result:

Assign Track user created workspaces to guide.

Workaround:

Solution: Update the assignment logic to stop assigning Track user created workspaces to a guide and assign them to Concierge.

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

Recording.3625.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @dylanexpensify

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022021886190709243937
• Upwork Job ID: 2021886190709243937
• Last Price Increase: 2026-02-12

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Krishna2323 (External)

[melvin-bot]

Current assignee @dylanexpensify is eligible for the Bug assigner, not assigning anyone new.

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022021886190709243937

[abbasifaizan70]

Proposal

Please re-state the problem that we are trying to solve in this issue.

When a user signs up with a new account (without + in the email), chooses Track and budget expenses and completes the flow, then goes to Workspace tab → Create workspace → Admins room, the workspace is incorrectly assigned to a guide instead of Concierge. The expected behavior is that Track user created workspaces should be assigned to Concierge.

What is the root cause of that problem?

The root cause is the assignment logic in ReportUtils.ts that decides whether onboarding tasks and messages are posted in the workspace #admins room (with a guide as the actor) or in the Concierge chat (with Concierge as the actor).

The function isPostingTasksInAdminsRoom() treats both MANAGE_TEAM (“Manage my team's expenses”) and TRACK_WORKSPACE (“Track and budget expenses”) the same: for users whose email does not contain +, it returns true for both. When it returns true, the app posts onboarding content in the #admins room and uses the assigned guide as the actor, so the workspace is effectively “assigned” to a guide. It should only return true for MANAGE_TEAM; for TRACK_WORKSPACE it should return false so that tasks and messages go to Concierge.

Code that caused the issue (permalink):

• isPostingTasksInAdminsRoom – included TRACK_WORKSPACE in the engagement choices that post in the #admins room and use a guide:

App/src/libs/ReportUtils.ts

Lines 12035 to 12046 in bc80c7b

	* Whether onboarding tasks should be posted in the #admins room instead of Concierge.
	* Onboarding guides are assigned to signup with emails that do not contain a '+' and select the "Manage my team's expenses" intent.
	*/
	function isPostingTasksInAdminsRoom(engagementChoice?: OnboardingPurpose): boolean {
	const userHasPhonePrimaryEmail = Str.endsWith(currentUserEmail ?? '', CONST.SMS.DOMAIN);
	return (
	engagementChoice !== undefined &&
	[CONST.ONBOARDING_CHOICES.MANAGE_TEAM, CONST.ONBOARDING_CHOICES.TRACK_WORKSPACE].includes(engagementChoice as 'newDotManageTeam' | 'newDotTrackWorkspace') &&
	(!currentUserEmail?.includes('+') || userHasPhonePrimaryEmail)
	);
	}

• Comment in prepareOnboardingOnyxData – documented that both MANAGE_TEAM and TRACK_WORKSPACE use the admins room / guide flow:

  • App/src/libs/ReportUtils.ts

    Lines 11373 to 11374 in bc80c7b

    	const shouldPostTasksInAdminsRoom = isPostingTasksInAdminsRoom(engagementChoice);
    	// When posting to admins room and the user is in the suggestedFollowups beta, we skip tasks in favor of backend-generated followups.

Because shouldPostTasksInAdminsRoom was true for TRACK_WORKSPACE, prepareOnboardingOnyxData targeted the #admins room and used assignedGuideAccountID as the actor instead of Concierge, which led to Track user created workspaces being assigned to a guide.

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

Solution: Restrict “post in #admins room / use guide” to MANAGE_TEAM only

Update the assignment logic so that only users who chose Manage my team's expenses (MANAGE_TEAM) get onboarding in the #admins room with a guide. Users who chose Track and budget expenses (TRACK_WORKSPACE) should get onboarding in the Concierge chat with Concierge as the actor.

function isPostingTasksInAdminsRoom(engagementChoice?: OnboardingPurpose): boolean {
    const userHasPhonePrimaryEmail = Str.endsWith(currentUserEmail ?? '', CONST.SMS.DOMAIN);
    return (
        engagementChoice !== undefined &&
        engagementChoice === CONST.ONBOARDING_CHOICES.MANAGE_TEAM &&
        (!currentUserEmail?.includes('+') || userHasPhonePrimaryEmail)
    );
}

Implementation

File: App/src/libs/ReportUtils.ts

1. isPostingTasksInAdminsRoom
   Change the condition so it returns true only when engagementChoice === CONST.ONBOARDING_CHOICES.MANAGE_TEAM (and the email condition is met). Remove TRACK_WORKSPACE from the set of choices that post in the #admins room. Update the JSDoc to state that only MANAGE_TEAM uses the guide/admins room; Track workspaces are assigned to Concierge.

2. Comment above shouldPostTasksInAdminsRoom
   Update the comment to say that only the MANAGE_TEAM onboarding action uses the #admins room (not TRACK_WORKSPACE).

Resulting behavior:

• MANAGE_TEAM (no + in email): isPostingTasksInAdminsRoom returns true → tasks and messages in #admins room with guide as actor (unchanged).
• TRACK_WORKSPACE: isPostingTasksInAdminsRoom returns false → tasks and messages in Concierge chat with Concierge as actor → Track user created workspaces are assigned to Concierge.

No other callers need to change; isChatUsedForOnboarding and the rest of the onboarding flow already depend on isPostingTasksInAdminsRoom, so they will behave correctly once TRACK_WORKSPACE is excluded from the admins-room path.

[ohrytskov]

🚫 Duplicated proposal withdrawn by 🤖 ProposalPolice.

[github-actions]

⚠️ @ohrytskov Your proposal is a duplicate of an already existing proposal and has been automatically withdrawn to prevent spam. Please review the existing proposals before submitting a new one.

[ohrytskov]

Proposal

Please re-state the problem that we are trying to solve in this issue.

After a user chooses Track and budget expenses and completes onboarding, creating a workspace from the Workspaces tab still assigns the workspace onboarding to a guide in #admins, instead of assigning it to Concierge.

What is the root cause of that problem?

The Workspaces-tab “create workspace” flow ignores the user’s onboarding purpose and creates the workspace as if the user selected Manage my team.

src/pages/workspace/WorkspaceConfirmationPage.tsx calls createWorkspaceWithPolicyDraftAndNavigateToIt(), which calls savePolicyDraftByNewWorkspace() in src/libs/actions/App.ts. That function currently hard-codes:

engagementChoice: CONST.ONBOARDING_CHOICES.MANAGE_TEAM,

So even if the user’s real onboarding intent was Track and budget expenses (PERSONAL_SPEND), this workspace is created with a “guide-eligible” engagement choice. For emails without a +, that results in the guide-assigned onboarding experience.

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

1. Plumb the user’s onboarding purpose into the Workspaces-tab creation path.

   • Read ONYXKEYS.ONBOARDING_PURPOSE_SELECTED in src/pages/workspace/WorkspaceConfirmationPage.tsx.
   • Pass it into createWorkspaceWithPolicyDraftAndNavigateToIt() (extend CreateWorkspaceWithPolicyDraftParams and SavePolicyDraftByNewWorkspaceParams with onboardingPurposeSelected?: OnboardingPurpose).

2. Use that purpose to select the correct engagementChoice in savePolicyDraftByNewWorkspace().

   • If onboardingPurposeSelected === CONST.ONBOARDING_CHOICES.PERSONAL_SPEND, pass engagementChoice: CONST.ONBOARDING_CHOICES.PERSONAL_SPEND.
   • Otherwise, keep the current behavior (MANAGE_TEAM) so unrelated flows don’t change.

3. Belt-and-suspenders: prevent the guide welcome message for Track users.

   • When onboardingPurposeSelected === CONST.ONBOARDING_CHOICES.PERSONAL_SPEND, also pass shouldAddGuideWelcomeMessage: false to createWorkspace(...).

This keeps the fix scoped to the Workspaces-tab create-workspace flow and avoids changing global onboarding behavior.

What alternative solutions did you explore? (Optional)