Features & settings

This page is for administrators. TaskFlow is modular — most capabilities are features you switch on — and this is where you manage them, along with instance-wide options.

Managing features

Admin → Plugins lists every feature with its source (built-in or added by you), its status — loaded, disabled, unavailable or failed — and a switch. Turning one on makes its pages, tabs and panels appear across the app; turning it off removes them and stops its background work within seconds. After changing the set, use Apply and reload so the interface picks up the change.

Features are off until you turn them on

A newly installed instance has its features disabled by default. Nothing loads, no background jobs run and no schedules fire until an administrator enables each one deliberately. If a feature you expect is missing, this is the first thing to check.

A feature can also show as unavailable: that means it isn't in the instance's allowlist and can't be enabled at all — see Configuration → Required in production.

Features you'll recognise from this documentation include search, notifications, custom fields, profile fields, checklists, templates, worklog, calendar, roadmap, releases, release waves, reports, dashboards, Service Desk, SLA, automation, webhooks, advanced permissions, archive, import, dev links, the Create menu, and the storage and email transports.

Global settings

Admin → Settings holds instance-wide options:

• Default interface language — the language new users get. Anyone's personal choice overrides it.
• Configuration modules — lightweight switches applied to the running system in seconds: closed registration and password sign-in disabled. See Users & permissions → Registration.
• Attachment storage — which storage backend holds issue attachments (see File storage).
• System email — which transport carries password resets and other account mail (see Email).
• Danger zone — see below.

The danger zone

Wipe all data erases the instance's content and reseeds the defaults. It exists for demo instances and for handing over a fresh installation, and it asks you to type a confirmation phrase.

This destroys your data

There is no undo. The operation is unavailable unless it has been deliberately permitted in the instance configuration — on a production instance leave it switched off, so an administrator cannot wipe live data by accident. Take a backup before using it anywhere you care about.

Audit log

Admin → Audit records actions across the system: who did what, to which object, when. Filter by category, actor, action, object identifier and date range.

Collection settings on the same page let you choose which categories of event are recorded at all. Narrowing this reduces noise and storage — but think twice before switching off security-related categories, since those are exactly the ones you'll want when investigating an incident.

AI & API control

TaskFlow can expose an MCP endpoint so external AI assistants work with your tracker. Admin → MCP controls it:

• Service status, and the list of available tools marked read or write.
• Kill-switches — switch the endpoint off entirely, or disable the write tools to leave read-only access. Changes apply within seconds and cut off connected assistants.
• A call journal — who used which tool, when, with what result and how long it took.

Admin → API tokens is the instance-wide view of every personal token, with revocation. See AI & API access.

Automation, webhooks and notifications

• Automation (Admin → Automation) — rules that react to events, schedules or a manual run. See Automation.
• Outgoing webhooks (Admin → Webhooks) — send events to external systems, with a delivery log and a test button. Requests to internal network addresses are blocked, so a webhook can't be used to probe your infrastructure.
• Notification gateways (Admin → Notification gateways) — route notifications to an external system such as a chat platform or an automation tool. Each gateway has its own URL, secret, event types and message templates per language. This page also selects the transport for notification email.

Email, storage and backups

Three areas have their own pages:

• Email — transports and which mail each one carries.
• File storage — where attachments and dumps live.
• Backups — schedules, retention and restore.

Import & archive

• Import (Admin → Import) — bring data in from Jira: users, groups, projects, issues, comments and attachments, with mappings for projects and field values, checked locally before the run starts. It's a one-way import, not a sync, and cancelling doesn't undo what was already created.
• Archive (Admin → Archive) — restore or permanently delete archived issues and projects, on separate tabs.

The Create menu

Admin → Create menu builds the Create dropdown in the top bar: entries with labels per language, an action (create a project, an issue or a board), a position, and visibility conditions by role, group or project. People only receive the entries that apply to them. An empty menu simply doesn't appear.

Changes are read when a page loads, so people see a reordered menu after a refresh.

Where to go next

• Users & permissions — accounts and access.
• Project configuration — types, workflow, fields.
• Self-hosting → Configuration — options set at deploy time.