Onboarding - Permission error appear, when try to complete any Concierge task

[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.11-15
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/TR-3916/folder/13176677/41237662/1158891316?sort=%2Bidentifier
Email or phone of affected tester (no customers): forexmater+7sdfsdddd81@gmail.com
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 10/Chrome
App Component: Other

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Create new account
3. Select "Manage my team's expenses" > "1-10" employees > "QBD"
4. Skip "Take us for a test drive"
5. Navigate to "Concierge" room
6. Click "Test drive" link at "Take a test drive" task
7. Click "Get started" button in the top of the page
8. Repeat steps 5-6
9. Select the checkmark at "Take a test drive" task
10. Open the new created "Take a test drive" chat with Concierge

Expected Result:

At the "Take a test drive" task, after click "Get started" button, or check the task it should be completed with no errors.

Actual Result:

"You don't have permission to take the requested action" error shows up, after try to complete and chehck the "Take a test drive" task.
Same bug is reproduced with all Concierge tasks.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @lydiabarclay (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[lydiabarclay]

@jponikarchuk was the DeployBlocker label added intentionally? If so, why?

[jponikarchuk]

@lydiabarclay I added DeployBlocker label because this issue is not reproducible in Production and not reproducible when Staging Server is off