IAO User - Changing Teams - Assignments Persist

* As an IAO user
* I want my remaining caseload to move with me when I change teams
* so that I do not have to manually re-assign my requests

**Assumptions & Scope**
As more IAO users and requests get brought into the system, we are running into a higher likelihood of analysts moving across teams. When analysts move across teams, they often keep some of their requests with them. When users change teams, their requests no longer appear - right now analysts have to go to their requests and assign them to themselves as part of their new team.

There are two scenarios to cover - one where an IAO analyst moves to a new team, and another where an IAO analyst has their access to the application revoked.

What is IN scope?
Request assignments for IAO users

What is NOT in scope?
Ministry user assignments should NOT persist requests across when they have to move teams (either to a new ministry, or to IAO)

**Acceptance Criteria**

**Scenario 1: IAO User Team Change - IAO**
* GIVEN an IAO user is assigned to a team
* AND they have requests assigned to them
* WHEN their group has been updated to a new IAO team
* THEN any existing assignment will move to the new team
*
**Scenario 2: IAO User - Access Revoked**
* GIVEN an IAO user is assigned to a team
* AND They have requests assigned to them
* WHEN they are removed from the team
* AND they are NOT added to a new IAO team
* THEN the requests will appear as un-assigned, in the relevant team queue tied to the Ministry (eg. Transportation request will show in the central and economy team as unassigned)

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

No implementation files, entry points, or tests are named. Start by locating the handling for IAO team membership and request assignments, then trace both team changes and access removal. Done means IAO assignments move to a new IAO team, while removed users' requests become unassigned in the relevant team queue without changing ministry-user behavior.

Written by the indexing model from the issue text.