nano SIEM
Settings

Settings

Supported in:Self-hosted

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

AreaPageNotes
Case Management (general, grouping rules, SLA, Self-run)Cases
Queues & Routing (Self-run)Cases
Notifications (Slack, Teams, PagerDuty, webhooks)Notifications
SOAR (Self-run)SOAROn/off switch, AI Judge budget, pack updates, notifications, private-network allowlist
AI & pivt (Self-run)AI & pivtProviders, models, guidance and usage
AreaPageNotes
Rarity ThresholdsRarity thresholds
Risk Scoring (Self-run)Risk scoring
SearchSearch settingsConcurrency, resource budgets, query safety
Storage & RetentionStorage & RetentionClickHouse retention and tiering; see also Disk pressure

Administration

AreaPageNotes
Access Control (users, groups, roles, API keys, sessions)Access control
Source VisibilitySource visibility
Single Sign-On (OIDC, Self-run)Single sign-onTrust changes need administrator authority
Agent Lane (Self-run)Agent LaneRead-only SQL access for AI agents: switch, tokens, revocation
Audit LogPlatform 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:retention and settings:ai_providers only 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.

What's next

On this page