Instance & operations

Instance settings

Administration → Instance settings changes how the whole installation behaves, at runtime and without a restart:

Group	Setting
Security	Minimum password length
	Require letters and digits
	Sign out after inactivity (minutes)
	Maximum session length (hours)
	Failed sign-ins before a temporary lock
	Lock window (minutes)
Public access	Allow public projects (off by default)
	Search engines and AI crawlers (indexing policy: all, search engines only, none)
Attachments	Maximum attachment size (MB)
	Blocked file extensions
Terminology	What issues are called (issue, work item, ticket, task)
Workflow	Workflow governance (any or constrained)
Announcement	Show announcement banner
	Banner style
	Banner text

Changes take effect within a few seconds on every server of a multi-node installation.

Features and modules

Features and modules turns parts of the product on or off for the whole instance: Service Desk, Dashboards, Automation, Approvals, Roadmap, Time tracking, Git integrations, Integrations, Intake, Wiki / Pages, Status updates, Views, Comment reactions, Initiatives, Milestones. A switched-off feature disappears from menus and its API answers “not found”; no data is deleted, so you can switch it back on. Installed modules (Timesheets, Plans, ITSM…) are enabled and disabled in the same place.

Appearance

Make the installation look like yours under Appearance: the product name, accent colour, logo and favicon (SVG files with scripts or external references are refused), and the footer links — including where “Documentation” and “Support” point. Changing branding is free; only removing the “Powered by Veqsio” credit needs the Enterprise licence. The link to the licence notices and the source code always stays.

Licence

The core of Veqsio is open source (AGPL-3.0). Modules and some features need a licence key: Licence → Apply key. The key is verified offline and never shown again. The page shows the licensee, plan, user limit, expiry and which Enterprise features are active. Plans: community (no key), team (audit export, issue security, Timesheets) and enterprise (everything). When a licence ends your data stays readable and paid behaviour switches off.

Audit log

Audit log records administrative changes: who did what, to which object, when and from where — never secrets or passwords. Filter by actor, action, target type and date range, search by target or path, see the changed fields of each entry, and export to CSV. Project archive/restore, imports, token and SSO changes, view exports and permission changes are all in it.

Configuration health

Configuration health “finds misconfiguration before your users run into it”. It also shows the heartbeat of each background job (last run, last success, failures and the last error), and the state of backups: Last backup and Last restore verification. If it says “No status file found”, run the backup script once. Make this page part of your weekly routine.

Backups and upgrades

Back up the PostgreSQL database and the attachment storage; Redis holds only transient data. The installer and the Docker Compose production stack include scripts for:

• Daily backups with rotation, and a restore verification that restores the latest backup into a scratch database and reports success on the health page. An untested backup is a hope, not a backup.
• Upgrades: re-run the installer (it dumps the database to the backups folder first, keeps your secrets, applies versioned migrations and restarts). A startup schema guard refuses to run against an outdated schema.
• Restore: stop the API, restore the dump, start again.

Decide your targets before an incident: how much data you can lose (RPO) and how long you can be down (RTO).

Monitoring

• /health and /ready probes for load balancers.
• A token-protected /metrics endpoint for Prometheus, with a ready-made Grafana dashboard.
• Structured JSON logs with a request id per request (X-Request-Id).
• Multi-node operation: set a role per node; scheduled jobs use advisory locks so they run once.

Configuration as code

Under Instance settings → Configuration as code export the instance settings, switched-off features and, per project, the public flag, project features, components and versions as JSON. Import a file with a preview: it lists the changes first, applies nothing if anything is invalid, matches components and versions by name and only adds. Workflows, schemes, custom fields, boards, roles and permission schemes are not covered yet.

AI assist

AI assist is off by default and can use self-hosted models. When enabled it offers similar-issue detection (works without any model), thread summaries, triage suggestions and release-note drafts. Text from outside is always treated as untrusted.

Public projects and search engines

With Allow public projects on, a project administrator can make a project readable without signing in (read-only; no e-mail addresses or internal comments; service desks excluded). Pages are server-rendered with canonical addresses, a sitemap and a Markdown view of each issue for AI tools; the indexing policy decides whether search engines may list them.

Progressive web app and push

Users can install Veqsio on a phone or desktop. Browser push uses keys generated per instance. Nothing needs to be configured.