01
Step one: explain permissions before the install
Start the guide with what the extension needs to read and why. Applicants hesitate when a browser prompt asks for access to pages. State plainly that the tool runs on job posting pages to find the title, company and link, and say what it does not collect. Worked example: Maya opens the store page, reads that the extension acts only when she presses its button on supported boards, and then installs with confidence. List the browsers supported, the pin-to-toolbar step, and where to find the setting that turns site access off or limits it later.
02
Step two: guide one real first capture
Do not describe every feature at the start. Send the reader to a live posting and ask for one action. Maya visits a posting for a project coordinator role, clicks the toolbar icon, and sees a small panel with the title, employer, location and a status field set to Interested. She adds a deadline and presses save. Include a screenshot placeholder for each stage and a line about what to do if the panel is blank, such as refreshing the page or filling the fields by hand. A single success moment teaches the habit better than a long tour.
03
Step three: confirm, correct and build the routine
Finish by showing where the saved record lives and how to fix it. Maya opens her list, finds the coordinator role, edits the pay range that was captured wrongly, and sets a reminder for the day before the deadline. Tell readers how to export the list, remove an entry and uninstall cleanly. Then suggest a weekly routine: save during the week, review on a fixed day, and archive roles that have closed. This closing section gives the guide lasting value, because it turns one installation into a repeatable way of managing applications.