Integration and workspace settings
Manage the connected board, enabled cycles, write mode, action cap, and confirmation threshold.
Settings → Integration is the dashboard control plane for the current organization.
Required permission: integrations:manage. Administrators receive it automatically; they can delegate it to another member under Settings → Access & Roles.
Integration fields#
| Field | Purpose |
|---|---|
| Board Type | Selects the Taiga or Jira adapter. |
| Project Key / Slug / ID | Identifies the target project. |
| Base URL | Identifies the provider API or site. |
| API Token | Replaces the encrypted board credential when a value is entered. |
| Enabled Cycles | Limits the dashboard-triggered cycle selection. |
Use Test Connection before saving a new or rotated credential.
Execution profile fields#
| Field | Purpose |
|---|---|
| Write mode | Chooses dry_run or, when the plan allows it, active. |
| Max Actions Per Run | Caps the action volume associated with a run. |
| Confirmation Threshold | Requires explicit confirmation when the planned action count reaches the configured threshold. |
Update settings safely#
- Record the current board and execution settings outside the application if your change process requires rollback evidence.
- Enter the new provider details or token.
- Select Test Connection.
- Keep write mode on
dry_runwhile validating a new board. - Use a conservative action cap and confirmation threshold.
- Select Save Settings.
- Complete a focused dry run and inspect its action log.
Provider token behavior#
The API encrypts stored tokens with Fernet. It does not return the raw token to the browser. Production startup requires an explicit encryption key and rejects insecure development cryptography when production guards are active.
Changing the SaaS integration does not update GitHub Actions or another standalone engine deployment. Rotate those credentials through their own secret store.