Use your own practice account and test data. Record an observation for each completion claim. You can print this worksheet or keep your answers in your own notes; this page does not submit them.
1. Choose what needs protection
What note are you testing, and how will you check that signed-out visitors cannot obtain it?
Review your work
Uses a fictional server-only note and states the lab’s signed-in-user audience.
Plans a direct signed-out request, rather than relying on a hidden page element.
2. Connect the ready protection
Which setup step is complete, and what actual app URL can you test?
Review your work
Identifies the running application address and completed server/provider configuration.
Reports a concrete setup blocker without publishing the private note or credentials.
3. Test the allowed audience
Who is allowed to read your practice note, and did the signed-in request match that rule?
Review your work
States that the lab permits any verified signed-in user, not only one note owner.
Records the allowed account’s result without extending this rule to personal account data.
4. Try the same route signed out
What did the direct signed-out and signed-in attempts each return?
Review your work
Compares the same note route with a signed-out request and an allowed signed-in request.
Checks that denied or failed responses contain no private note text.
5. Protect one more test value
Provide the new value’s protection and the observed access results.
Review your work
Keeps both fictional values server-only under the stated shared-member rule.
Retests allowed, denied and service-failure responses for the added value.