---
title: "Unfollow a record without removing collaboration access"
description: "Verify that removing a test record subscription stops its follower state while preserving the member ability to view and edit under an independent role."
canonical_url: "https://vostride.com/agent-library/collaboration/subscription-removal-keeps-access.md"
md_url: "https://vostride.com/agent-library/collaboration/subscription-removal-keeps-access.md"
content_kind: "recipe"
topic: "collaboration"
---

# Unfollow a record without removing collaboration access

Verify that removing a test record subscription stops its follower state while preserving the member ability to view and edit under an independent role.

## Risk

Following and authorization are separate concepts. An implementation can accidentally remove access alongside a subscription, or leave the visible follower indicator out of sync with saved subscription state.

## Fixtures

- A test issue grants the QA member Editor access through its project role and separately lists that member as a follower.
- The fixture inventory records the role grant and subscription as two distinct relationships.
- The issue contains synthetic text and uses a non-delivering notification environment for any follow-state effects.

## Steps

1. Open the issue and verify the QA member is shown as Following while the project role permits editing.
2. Choose Unfollow and verify the control changes to Follow without closing the issue.
3. Reload the issue and verify the unfollowed state persists and the content remains accessible.
4. Make a small fixture-only description edit, save, and verify the change persists under the unchanged Editor role.
5. Run the prepared relationship check and verify the subscription is absent while the project role grant remains unchanged.

## Expected results

- The follower relationship is removed for the intended member and issue.
- The independent project role remains Editor and still authorizes the fixture edit.
- The visible follow control agrees with the saved subscription state after reload.

## False-pass traps

- A readable cached issue can mask lost access; a reload and authorized edit check exercise the remaining permission.
- A changed button label alone does not prove the stored subscription was removed.

## Cleanup

- Restore the description and original subscription if the issue is reused, or delete the fixture issue.

## 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 first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Collaboration QA recipes](/agent-library/collaboration.md)
- [Software factory QA library](/agent-library.md)