Expose all Approval Path admin settings in the Web API with per-tab API key permissions

Description

Problem

Today an admin can manage Approval Path settings only in the UI. The Web API covers only approvals, definitions and conditions. A script or an AI tool (Rovo, MCP) cannot configure the app, move a configuration between sites, or read the settings for an audit. API key permissions also cover only approval operations, so there is no way to issue a key that can reach just one part of the settings.

Change

  • The Web API can read and change everything an admin manages in the UI: every Settings section (General, Permissions, Notifications, Email, Message Templates, Page Versioning, JSM, Approval Expiration, Work mapping, Webhooks, Slack, AI), plus Delegations, API Keys, Activity and Instance Errors.

  • The Web API also covers the space (Confluence) and project (Jira) level settings that a space/project admin sets in the UI.

  • The new endpoints are added to the existing Web API v2, with no new API version. Existing calls keep their contract.

  • An API key gets permissions per admin tab and operation (read, list, create, edit, delete). Each tab shows only the operations it supports.

  • In the API Keys form, tabs are rows and operations are columns, with a "select all" option.

  • Existing keys keep their current approval permissions.

  • Secrets (e.g. SMTP password, Slack tokens, AI keys) are write-only and never returned by the API.

  • A key can create or edit another key only with permissions it has itself.

  • Activity shows changes made with a key as "API key: <name>".

Out of scope

  • Narrowing keys to the permissions they actually used (as in ESFJ-2553). If needed, it goes into a separate ticket.

Open questions

  • Do Definitions and Conditions (already in the Web API) move to the per-tab permission model, or do they keep the current key permissions?

  • Does a key act as an admin or through its performer (as it does today for approvals)? This changes who can change space/project settings.

  • Should key narrowing be part of this ticket, as in ESFJ?

Acceptance criteria

  • Every setting an admin can change in the UI (global and space/project) can be read and changed through the Web API with the same effect as in the UI.

  • A call without the permission for that tab and operation is rejected and the setting stays unchanged.

  • The API cannot change anything the UI cannot change, and cannot bypass UI validation.

  • GET responses never contain secrets. Writing a new secret value works.

  • A key cannot create a key with broader permissions than its own.

  • A key created before this change still performs the same approval operations as before, and existing Web API v1 and v2 calls work unchanged.

  • A change made through the API appears in Activity with the key name.

  • The new endpoints are described in the published OpenAPI document.