Settings
Every area under Settings, what it controls, and which areas aren't in the open-source edition.
Use Settings (/settings) to configure your workspace, detections, and administration controls. Your permissions and deployment determine which areas you can open and change.
Who can change settings
Every nano deployment is a single tenant with its own ClickHouse and PostgreSQL, so every setting you have permission for is editable. Areas marked Self-run are included with nano Self-run; the open-core build doesn't include them.
Settings areas
Workspace
| Area | Page | Notes |
|---|---|---|
| Case Management (general, grouping rules, SLA, Self-run) | Cases | |
| Queues & Routing (Self-run) | Cases | |
| Notifications (Slack, Teams, PagerDuty, webhooks) | Notifications | |
| SOAR (Self-run) | SOAR | On/off switch, AI Judge budget, pack updates, notifications, private-network allowlist |
| AI & pivt (Self-run) | AI & pivt | Providers, models, guidance and usage |
Detection & Search
| Area | Page | Notes |
|---|---|---|
| Rarity Thresholds | Rarity thresholds | |
| Risk Scoring (Self-run) | Risk scoring | |
| Search | Search settings | Concurrency, resource budgets, query safety |
| Storage & Retention | Storage & Retention | ClickHouse retention and tiering; see also Disk pressure |
Administration
| Area | Page | Notes |
|---|---|---|
| Access Control (users, groups, roles, API keys, sessions) | Access control | |
| Source Visibility | Source visibility | |
| Single Sign-On (OIDC, Self-run) | Single sign-on | Trust changes need administrator authority |
| Agent Lane (Self-run) | Agent Lane | Read-only SQL access for AI agents: switch, tokens, revocation |
| Audit Log | Platform audit | |
| GDPR & Compliance | — | Erasure runs as a queued background job |
Also documented here:
- Disk pressure: automatic eviction of the oldest daily ClickHouse partitions when local disk fills up.
- Detection-as-Code push targets, configured under Repositories: AI tuning opens pull requests in your rules repository.
Air-gapped Import appears only on air-gapped installs.
Changing settings safely
- Settings changes are recorded in the audit log. Review it after configuration work.
- Grant
settings:system,settings:retentionandsettings:ai_providersonly to administrators. See Access control. - Settings can't be exported or imported as a bundle. To keep detections in version control, use Detection-as-Code.
Troubleshoot
Need help with these checks? Contact support with the request ID and time with timezone.
A setting won't save
Check that your role holds the permission for that area (for example settings:system, settings:retention or settings:ai_providers). Areas marked Self-run aren't available in the open-core build.