Coming soon. The Wiki is in active development, so features and these docs may still change. Early adopters: contact us for access.

Support

How to get help, what to send with a support request, and how to report a security problem

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

  1. Check the system check — Settings → Advanced → System check often names the problem (Pro).
  2. Check known issues — Known issues and the FAQ may already have the answer.
  3. Check the server log — Errors carry a request ID; the log line with it says what went wrong.
  4. If the server can't start — It runs in recovery mode, which lists what's wrong.

2. What to send

WhatWhere to find it
Version, build and the server that answered? → About → Copy details, or the footer's copy button
Your licence IDSettings → Application → Licensing
Single server or cluster, and how many serversSettings → Clustering
What you did, what you expected, what happenedSteps to reproduce; the exact error, with its request ID
When it started, and what changed thenAn upgrade, a setting, the proxy, the identity provider
Logs from the time it happenedSettings → Logging → Files → export, or your log platform
For editing problemsThe 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

SeverityMeaningExamples
1 — CriticalProduction down or data at risk; no workaroundNo server starts; pages can't be read
2 — HighA major function fails; a workaround is hardNobody can edit; single sign-on fails for everyone
3 — NormalA function doesn't work as documented; a workaround existsAn import fails; a setting doesn't apply
4 — LowQuestions, documentation, feature requestsHow 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.