Vectored supports the Wiki. Write to support@vectored.dev, or use the form at vectored.dev/#contact. Licences, renewals and changes of tier go the same way.
The Wiki isn't released yet. Early adopters: contact us for access to get the server and a licence.
1. Before you write
- Check the system check — Settings → Advanced → System check often names the problem (Pro).
- Check known issues — Known issues and the FAQ may already have the answer.
- Check the server log — Errors carry a request ID; the log line with it says what went wrong.
- If the server can't start — It runs in recovery mode, which lists what's wrong.
2. What to send
| What | Where to find it |
|---|---|
| Version, build and the server that answered | ? → About → Copy details, or the footer's copy button |
| Your licence ID | Settings → Application → Licensing |
| Single server or cluster, and how many servers | Settings → Clustering |
| What you did, what you expected, what happened | Steps to reproduce; the exact error, with its request ID |
| When it started, and what changed then | An upgrade, a setting, the proxy, the identity provider |
| Logs from the time it happened | Settings → Logging → Files → export, or your log platform |
| For editing problems | The browser and its version, and whether /api/ws reaches the server |
Never send CONFIG_ENCRYPTION_KEY, passwords, API tokens, calendar addresses, licence files or backups. Log exports are redacted, but look through anything before you send it.
3. Severity
| Severity | Meaning | Examples |
|---|---|---|
| 1 — Critical | Production down or data at risk; no workaround | No server starts; pages can't be read |
| 2 — High | A major function fails; a workaround is hard | Nobody can edit; single sign-on fails for everyone |
| 3 — Normal | A function doesn't work as documented; a workaround exists | An import fails; a setting doesn't apply |
| 4 — Low | Questions, documentation, feature requests | How to configure something |
4. Security problems
To report a vulnerability in the Wiki, email security@vectored.dev (or support@vectored.dev with Security in the subject) instead of discussing it in public. Include what you found, how to reproduce it, and the version.
5. Your own help desk
If your team supports the Wiki's users itself, point the ? menu's links at your own service desk: Settings → General → Help menu. A mailto: link fills in the version and server for the person writing.