Requirements chat opens after you raise a request while viewing as a customer

When you raise a request as a customer, the platform takes you straight into the requirements chat, where the assistant works through what you actually need before anything moves forward.

If you were an admin using View as to walk through the customer experience — the way the demo tenant is presented — that last step broke. The request was created correctly, but the page it sent you to reported that it could not be found, and the walkthrough stopped at the one moment it was meant to show off. The request was never lost: opening it again from the projects list worked.

The requirements page was checking the request against your own account rather than against the customer you were viewing as, so it did not recognise a request you had just raised on their behalf. It now checks against the person you are viewing as, which is who the request belongs to — and which is already how every action on that page behaved.

Nothing changes for a customer working in their own session; the flow there was always correct.