BasicSec.org

IntroductionContentsReviewsToolsUpdatesPurchaseContact
Home / Practical guides

An unexpected password reset in the volunteer inbox

· · Worked example and worksheet

The treasurer gets a reset code for the club’s shared mailbox during rehearsal. Nobody on shift asked for it. The message alone cannot tell the treasurer who triggered it or whether anyone got in. What matters first is whether anyone used the code and what the account itself shows.

1. Use the sign-in route the group already knows

Leave the link and phone number in the message alone. Use a saved bookmark, the service’s usual app or a website address you already know. If the account belongs to an organization, use the administrator contact in your own directory. The Microsoft phishing guidance explains why an independently obtained address or number matters even when a message looks familiar.

Check which account the message names. A former volunteer’s personal address and the club mailbox need different account owners. If ownership is unclear, the group account inventory can help you find the person responsible without passing a code around.

2. Match the response to what happened

3. Leave the next volunteer a decision they can follow

A fictional entry for the rehearsal incident might read “18:10 — code arrived. Nobody on shift used it. Treasurer contacted the mailbox owner using the club directory. Owner to review account activity before tonight’s handoff.” Keep the code, passwords and recovery addresses out of the note.

The three sample handoff notes show how the owner’s next action changes with the evidence. For the separate job of keeping recovery materials available between shifts, see what belongs in the account recovery envelope.

IntroductionContentsReviewsToolsUpdatesPurchaseContact
Analytics privacy
Microsoft Clarity / Privacy