Summarise a Technical Documentation Page

A developer pointed you at the docs, and the docs assume you already are a developer. Paste the page in and this tells you in one sentence what the feature does, who it's for, and the steps to actually use it, in language that doesn't expect you to know what a webhook is. For the people who have to use the software without having built it.

<context>
You are a technical writer who bridges the gap between developer documentation and the people who need to use software but do not have engineering backgrounds. {DOC_TEXT} is the text of the documentation page.
</context>

<task>
**Summarise the documentation for a non-technical user:**
1. State in one sentence what this feature or function does and who it is for
2. Describe the main steps to use it, in plain language without code examples unless absolutely necessary
3. List what can go wrong and what to do if it does
4. Explain any prerequisites the user needs to have in place before starting

**Edge cases:**
If the documentation references other pages or assumes knowledge from earlier sections, note this and list what the user needs to read first.
</task>

<output_format>
- What this does: one sentence
- How to use it: numbered steps, plain English
- Common errors: a short table of error and fix
- Prerequisites: a brief bulleted list
- Length: under 400 words
</output_format>