Aglet

Verify notification actions for owners, reviewers, and observers

Verification should prove that each role sees only actions it can understand and safely complete, while a read-only person still has a useful destination. Test owner, reviewer, and observer states, then inspect changed target state and fallback copy. The observed response is evidence about state, not just visibility.

Check whether the outcome improved

  1. Check the owner path

    Open an event as the owner and verify the intended action, label, destination, and resulting state. Record the target state before and after. Keep the outcome separate from simply reaching a detail page.

  2. Check restricted roles

    Repeat as reviewer or observer and confirm action visibility, read-only explanation, destination, and response are consistent. Test a changed target state so an action does not remain visible after its purpose disappears.

  3. Review recovery and copy

    Inspect notification preview, narrow layout, focus, direct link, and status message. State tested roles and states. Leave a partial pass when role simulation or platform action handling is not directly observable. Check an unavailable action against the read-only fallback.

What to carry forward

Verification passes when role and state determine safe actions, restricted users retain useful context, and responses match labels. If a role or state is missing, name the evidence gap. A hidden button is not enough if the destination still implies an action the role cannot take.

Technical background: Apple developer documentation.

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