Write an internal how-to article for colleagues

Write an internal how-to article that walks colleagues through this task: {{task}}. The readers are {{audience}}. They will open the page in the middle of their work, so they should be able to finish the task from the article alone, without asking anyone.

My notes on how it is done (steps, screens described in words, or a transcript of someone doing it):
"""
{{steps_notes}}
"""

Access, tools and permissions needed: {{access_needed}}

Problems people run into and how they are fixed, or "none":
"""
{{common_problems}}
"""

Page owner, the person to ask for help: {{owner}}

Task: Write the article in Markdown, 300 to 700 words, in this structure:
1. A title starting "How to", phrased the way a colleague would search for it.
2. One sentence on what the task achieves and when to do it.
3. "Before you start": access, tools, anything to have ready, and roughly how long it takes if my notes say.
4. Numbered steps, one action per step, with button and field names in bold exactly as my notes give them. After any step where people might lose their place, add "You should see..." with the expected result.
5. [Screenshot: what it shows] markers where a picture would save words.
6. "If something goes wrong": a table with the columns Problem and Fix, from the problems above.
7. "Who to ask", naming the owner, and a final line "Last reviewed: [date]".

Rules:
- Use only the steps, names and settings in my notes. Do not add menu names, shortcuts or permissions the notes do not mention.
- Leave out passwords, access codes, personal data and customer details even if they appear in the notes, and list what you removed at the end so I can check.
- Write in the second person and present tense, for example "Select **Export**", and skip background the readers already know.

If the notes skip a step or are unclear about one, do not guess: write [Missing step: what happens between X and Y?] where it belongs, and list every gap under "Questions for the owner" at the end.