Support
Support docs should make license boundaries, support scope, FAQ, and escalation paths clear before buyers customize production code.
On this page
Support policy outline
| Topic | Document |
|---|---|
| License | What the buyer can use, modify, deploy, resell, or redistribute. |
| Support scope | Which setup, billing, deployment, and customization questions are covered. |
| FAQ | Common buyer questions about Supabase, payments, email, admin, updates, and customization. |
| Escalation | What information to include: repo version, env area, provider, logs with request id, reproduction steps, and checks already run. |
Support request checklist
- Describe the exact route, feature, provider, or job involved.
- Include request id, provider event id, job id, or profile id when available.
- Say whether the issue is local, preview, or production.
- List the commands already run.
- Do not paste secrets, raw tokens, or full provider payloads.