---
title: "Verify resource ownership transfer updates both users permissions"
description: "Transfer a test-owned resource between accounts and check the old and new owners against the documented post-transfer permission rules."
canonical_url: "https://vostride.com/agent-library/authorization/resource-owner-transfer.md"
md_url: "https://vostride.com/agent-library/authorization/resource-owner-transfer.md"
content_kind: "recipe"
topic: "authorization"
---

# Verify resource ownership transfer updates both users permissions

Transfer a test-owned resource between accounts and check the old and new owners against the documented post-transfer permission rules.

## Risk

Ownership transfer is a permission transaction, not only a label update. Stale ownership caches can leave the previous owner with exclusive actions or fail to grant the recipient the controls needed to manage the resource.

## Fixtures

- Two test-owned accounts in an organization that permits resource ownership transfer.
- A disposable resource with a known initial owner and an explicit role matrix for old and new owners.
- Ownership and permissions inspection hooks plus separately executed browser runs for each account.

## Steps

1. As the current owner, open resource settings and verify the ownership label and transfer control.
2. Transfer ownership to the intended fixture recipient using the product confirmation flow; verify the resulting owner label.
3. Run the ownership hook and verify the stable resource identifier now names the recipient as owner, with no duplicate resource created.
4. In the recipient account run, open the same resource and verify an owner-only reversible setting can be changed and persisted.
5. Return in an old-owner run and verify its remaining controls and direct settings access match the documented retained-member or removed-owner policy.

## Expected results

- The existing resource changes owner without losing its identity or contents.
- The recipient receives the documented owner permissions.
- The former owner loses only the permissions specified by the transfer policy.

## False-pass traps

- An updated ownership label does not prove downstream actions use the new permission state.
- Assuming the old owner must lose all access ignores products that intentionally retain ordinary membership.

## Cleanup

- Transfer the fixture resource back or delete it using the designated cleanup account.

## 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)

- [Authorization and permission QA recipes](/agent-library/authorization.md)
- [Software factory QA library](/agent-library.md)