Establish what is happening
Capture the invitation state
Record the redacted recipient class, workspace name, intended role, invitation status, expiry state, and page message. Note whether the recipient is signed in, has another workspace, or is a new account. Do not retain a raw invitation URL or personal email address.
Exercise acceptance variants
Open a fresh invitation as a new user, an existing member, a user in another workspace, an expired recipient, and an already-accepted recipient where fixtures permit. Compare redirect, workspace context, role explanation, and resulting membership without mixing attempts.
Check the visible decision
Mark whether the page clearly identifies who invited the recipient, which workspace is involved, what accepting grants, and what to do when the invitation is invalid. Record any mismatch between displayed role and authorized membership as a separate access finding.
What to carry forward
Triage is complete when the invitation lifecycle, recipient session, workspace, role, visible decision, and resulting membership are recorded. If the stored invitation cannot be inspected safely, mark acceptance or expiry as unknown rather than inferring the cause from a confusing email.
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