Tenant settings
The Settings page holds tenant-wide values that govern how Webhooks Pro delivers, retries, and retains. Policy is global, configuration is per-webhook. Changes take effect immediately after Save — no restart needed.
What's tenant-wide vs. per-webhook
This is the rule worth internalising:
Lives on Tenant settings (one value for the whole site) | Lives on the Webhook form (one value per webhook) |
|---|---|
Run-again button ranges | URL, HTTP method |
Auto-disable on failure threshold | HTTP headers, query params |
Request timeout | Payload template choice |
Debounce window | Events + JQL filter |
Logs auto-refresh interval | Schedule (CRON) |
Log retention | HMAC signing secret |
Debug logging toggle | Active / disabled state |
Schema migrations | Workflow transition bindings |
Backup / Restore |
|
Atlassian platform status (read-only) |
|
Subscription / SEN (read-only) |
|
Translation: the Settings page sets the delivery and retention policy; each webhook owns what it sends, where, when, and how it's authenticated. Full breakdown: Tenant-wide vs per-webhook scope.
Tabs
The Settings page has eight tabs. Some are settings, some are operational panels.
Tab | What's there |
|---|---|
Webhooks | Run-again ranges, Auto-disable threshold, Request timeout, Debounce window |
Logs | Auto-refresh interval, Log retention, Debug logging, Prune now |
Schema | Schema migration runner (operational) |
Status | Atlassian platform health dashboard (read-only) |
Language | Admin UI language |
Migration | One-shot data migration helpers |
Backup | Export / import every webhook + payload template |
About | Subscription card (live) + License & Credits (static) |
The About tab is documented in Subscription states and SEN. Backup is the same JSON bundle you can export from the Webhooks page or the Payload Templates page, just with a wider scope.
Sub-pages
Saving
Save changes — primary button. Only enabled when the form is dirty. Shows "Saving…" while in flight; success banner auto-dismisses after ~3 s.
Cancel / Discard changes — reverts to the last saved state.
Reset to defaults — fills the form with built-in defaults (does not save — you still have to click Save).
Keyboard: Ctrl+S / ⌘S when the form is dirty.
Tenant-wide values are picked up by every running webhook on its next delivery. There's no in-flight migration to worry about.
Default values
Setting | Default |
|---|---|
Run-again button ranges | All ranges enabled |
Auto-disable on failure | Disabled (never auto-disable) |
Request timeout | 30 seconds |
Debounce window | 25 seconds |
Logs auto-refresh interval | 30 seconds |
Log retention | 14 days |
Debug logging | Off |
Defaults are intentionally conservative: out of the box, nothing auto-disables, nothing logs verbosely, and the debounce window is short enough that admins see deliveries within a minute.
Common patterns
"I want webhooks to fail fast when receivers are slow"
Setting | Value |
|---|---|
Request timeout | 10 seconds |
"I want auto-disable to protect a flaky receiver from runaway failures"
Setting | Value |
|---|---|
Auto-disable on failure | 5 failures |
The counter resets on the first success — flaky behaviour with occasional successes won't trip it. See Auto-disable thresholds.
"I need 30 days of audit logs"
Setting | Value |
|---|---|
Log retention | 30 days |
"Receivers should batch a burst of edits, not see them all"
Setting | Value |
|---|---|
Debounce window | 60 seconds |
"I'm troubleshooting with support — verbose Forge logs"
Setting | Value |
|---|---|
Debug logging | On |
Switch off after the support session — verbose traces include full event payloads.
Related
Tenant-wide vs per-webhook scope — full breakdown.
Retry ranges — what shows the Run again button.
Auto-disable thresholds — the protection switch.
Delivery timeouts — fail fast vs. wait.
Settings retention — what retention controls.
Webhooks — the per-webhook configuration these settings apply to.
Subscription states and SEN — the About tab.