Aglet

How to verify workspace invitation acceptance

Verification must prove that a recipient can identify the workspace and role before acceptance and that every lifecycle state ends safely. Run new-account and existing-account variants, because an invitation that works for a signed-out visitor may still confuse a member of another workspace.

Check whether the outcome improved

  1. Verify the invitation preview

    Open a synthetic invitation while signed out and signed in. Assert the page names the intended workspace, role, inviter context when available, and action required before membership changes. Ensure raw tokens and unrelated workspace data do not appear in the rendered page.

  2. Verify lifecycle outcomes

    Accept a fresh invitation, revisit an accepted invitation, use an expired fixture, and exercise a duplicate or revoked state when available. Assert clear messages, safe redirects, and exactly the intended membership and role. Record any lifecycle branch the harness cannot create.

  3. Verify context isolation

    Open an invitation while the recipient has another workspace selected and follow back links after acceptance. Assert the resulting pages and membership queries remain scoped to the invited workspace. Test keyboard focus and narrow layout on the decision page if it contains controls.

What to carry forward

Accept when recipients see an accurate workspace and role before acceptance, lifecycle failures explain recovery, and the resulting membership remains tenant-scoped. Mark unsupported invitation variants partial rather than treating a successful fresh acceptance as full coverage.

Keep the decision with the work.

Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.

Create an account See the product workflow