Preview features¶
Not everything in Vesana is stable yet. Areas still under active development are switched off by default on every instance — completely: no menu entry, no page, no API. They only exist once you enable them in the admin area.
You find the switch under Admin → System → Preview features (super admins only).
What is preview?¶
| Area | What it does | When off |
|---|---|---|
| Reports (PDF + SLA) | Scheduled PDF reports by e-mail and SLA evaluations (PDF, SLA) | No report is generated or sent |
| Status Pages | Public status pages at /status/<slug> (docs) |
The public links answer 404 as well |
| Wiki | Internal knowledge base with articles, folders and links to checks; the AI uses it as a source (docs) | No menu entry, no wiki button on checks (error overview, host detail), no wiki source and no "Save as wiki article" in the AI, no quick-search hits; embeddings are not computed |
| SSO (OIDC) | Sign-in through an identity provider (Entra ID, Keycloak, Authentik …) including just-in-time provisioning and group mapping (docs); sign-in with a domain account via Active Directory / LDAP belongs to it too | The SSO buttons on the sign-in page and the admin tab disappear, directory sign-in is off; the providers stay stored. Careful: accounts that only sign in through the identity provider can no longer get in |
Anomalies & forecasts
Since October 2026 an official feature with its own switch under Admin → System → Anomalies & forecasts — see Anomalies & forecasts.
Each area has its own switch. A switch takes effect immediately, without a restart — for every user of the instance.
What "off" means exactly¶
- The menu entry is missing, for super admins too. A direct link ends up on the start page.
- The API answers with 404 (
PREVIEW_FEATURE_DISABLED) — not 403. The area simply does not exist on this instance. - The related background jobs pause.
- Data you already created is kept. Report schedules, status pages and wiki articles are back the moment you switch the area on, exactly as you left them.
What happens on update¶
Anyone who was already using one of these areas before updating to v1.9.445 (created report schedules or status pages) keeps it enabled — nothing disappears without a word. Fresh installations start with everything off. Anomaly detection was off by default before; its switch merely moved here (the old "Anomaly Detection" tab redirects).
The wiki became a preview feature with v1.9.453. It stays enabled after that update if there is at least one article you wrote yourself. The bundled guides do not count — every instance has them.
SSO (a preview feature since v1.900.0) stays enabled as soon as at least one identity provider is configured — including a disabled one. That is deliberate: such an instance may have accounts without a password that can only sign in through the provider. They would otherwise be locked out by the update.
Policies no longer exist; the area was removed with the update. What policies had created is kept: assigned tags are now normal tags on the device, created checks are normal checks. Policies that adjusted check configuration (config_patch) no longer take effect — for each one that was still active, a warning is written to the diagnose log (category "Check change", type policy_config_patch_removed), so you can carry the adjustment over to the check or profile directly if needed.
In the portal layout the affected menu entries carry a Preview badge. As long as an area is off there is no visibility switch for it — it is not there in the first place.
Why so strict?¶
An area that is only missing from the menu but still reachable via URL or API would be cosmetics. Whoever uses a preview should do so deliberately — and report back via the feedback button. Once an area is stable, its switch disappears and it is simply there.
Automated setup
"Set up automatically" was briefly a preview feature as well. It has since been removed entirely; the update ends any open runs. New instances show a welcome overview on the start page instead.