Decide where the work belongs
Classify the harm
Elevate a link that can create membership in the wrong workspace or present the wrong role above a message that is merely verbose. Treat a blocked valid recipient, expired invite, duplicate invite, and already-accepted state as separate queue types with distinct owners.
Bound the affected journey
Record sender role, recipient state, workspace count, browser, link age, and route where the issue appears. Use synthetic accounts and identified reports only. If the number of affected invitations is unknown, preserve that uncertainty instead of extrapolating from one fixture.
Choose safe recovery
Prefer a page that names the workspace and role before acceptance and provides a safe expired or wrong-account next action. Do not encourage a recipient to guess between workspaces. Assign permission findings to the existing authority owner and copy findings to the onboarding owner.
What to carry forward
Queue wrong-workspace or wrong-role evidence first, then valid recipients who cannot recover, then message clarity. Include the invitation state, safe next action, affected variant, owner, and test evidence that would change the priority before closing.
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