---
title: "Verify organization switching updates lists and creation scope"
description: "Switch between two test organizations containing similarly named records and confirm the active organization controls displayed data and newly created resources."
canonical_url: "https://vostride.com/agent-library/organization-membership/organization-switch-context.md"
md_url: "https://vostride.com/agent-library/organization-membership/organization-switch-context.md"
content_kind: "recipe"
topic: "organization-membership"
---

# Verify organization switching updates lists and creation scope

Switch between two test organizations containing similarly named records and confirm the active organization controls displayed data and newly created resources.

## Risk

An organization switcher may update its label before the application data or mutation scope catches up. Distinct fixture markers expose stale lists and wrong-tenant creation without relying on cosmetic color or avatar differences.

## Fixtures

- One test-owned account belonging to organizations Amber and Blue with creation permission in both.
- A record named Shared Name in each organization, with different description markers.
- A resource inspection hook that reports organization identifiers for the run-created record.

## Steps

1. Open Amber and verify its switcher label and Shared Name record description marker.
2. Switch to Blue using the visible organization control and verify Blue label and Blue-specific record description after loading completes.
3. Search for the Amber-only marker and verify it does not appear in Blue scoped results.
4. Create a uniquely named record while Blue is active and verify it appears after reload in Blue list.
5. Switch back to Amber and verify the new record is absent there; inspect its stored organization identifier through the hook.

## Expected results

- Lists and detail pages reflect the selected organization after switching.
- The newly created record belongs to Blue stable organization identifier.
- Amber retains its original data without receiving the Blue-created record.

## False-pass traps

- A changed organization label alone does not prove queries and mutations changed scope.
- Identical fixture descriptions would make stale organization content visually indistinguishable.

## Cleanup

- Delete the run-created record and restore the account initial organization selection if fixture policy requires it.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa auth state](/docs/agent-qa/guides/auth-state.md)

- [Organization membership QA recipes](/agent-library/organization-membership.md)
- [Software factory QA library](/agent-library.md)