Access Control
Users, groups, roles, permissions, API keys and sessions in nano.
Use Settings → Access Control to manage users, groups, roles, API keys, and sessions. A user's permissions are the union of the roles assigned to their groups.
The page has five tabs: Users, Groups, Roles, API Keys, and Sessions.
Two related controls have their own pages:
- Source Visibility decides which data a group can see. Roles decide what actions a user can take.
- Single Sign-On connects an OIDC identity provider.
Users
Administrators create local users with an email, name, password and initial groups.
- Passwords: at least 12 characters, with an uppercase letter, a lowercase letter, a digit and a special character.
- Lockout: 5 failed sign-ins lock the account for 15 minutes. An administrator can unlock it early.
- Status: Active, Locked (failed sign-ins) or Disabled (by an administrator; can't sign in until re-enabled).
- Actions: create, edit, unlock, disable or enable, and delete. Delete can't be undone.
Users who sign in through SSO are created on first sign-in. Their email and password belong to the identity provider. See Single Sign-On.
Multi-factor authentication
nano supports TOTP authenticator apps (RFC 6238, 6-digit codes) with backup codes. Each user enrolls from their own profile. An administrator can reset a user's MFA.
An administrator can require MFA for every user from the MFA panel in Access Control.
Groups
Groups hold users and carry role assignments. Every member of a group inherits all of its roles. A user can be in several groups.
- Everyone is a built-in group that every user belongs to. It can't be deleted.
- Create custom groups for teams, for example "SOC Tier 1" or "Detection Engineering".
- Deleting a custom group removes the roles it granted. Its users are kept.
Groups are also the unit for Source Visibility grants and, on Self-run, for SSO group mappings.
Roles
A role is a named set of permissions. Assign roles to groups, not to individual users.
Built-in roles
| Role | Description |
|---|---|
| Admin | Full system access with all permissions |
| Editor | Create and manage detections, parsers and dashboards |
| ReadOnly | View-only access for search and monitoring |
To see exactly what a role grants, open it in the Roles tab.
Custom roles
Users with roles:create can build custom roles from any of the permissions below, for example an "Alert Triage" role with search:view, search:execute, alerts:view, alerts:acknowledge and alerts:assign.
Permissions
Permissions are area:action strings. GET /api/permissions returns the full list your deployment knows.
| Area | Permissions |
|---|---|
| Search | search:view, search:execute, search:save, search:share, search:sql |
| Dashboards | dashboards:view, dashboards:create, dashboards:edit, dashboards:delete |
| Artifacts | artifacts:view, artifacts:create, artifacts:edit, artifacts:delete |
| Notebooks | notebooks:view, notebooks:create, notebooks:edit, notebooks:delete, notebooks:share, notebooks:agent_record |
| Detections | detections:view, detections:create, detections:edit, detections:delete, detections:promote, detections:export |
| Alerts | alerts:view, alerts:acknowledge, alerts:close, alerts:assign |
| Cases | cases:view, cases:create, cases:edit, cases:delete, cases:assign, cases:close, cases:comment, cases:share |
| Hunts | hunts:view, hunts:manage, hunts:run, hunts:triage, hunts:report, hunts:profile_write |
| Playbooks | playbooks:view, playbooks:manage, playbooks:run, playbooks:publish |
| Parsers | parsers:view, parsers:create, parsers:edit |
| Log sources | log_sources:view, log_sources:create, log_sources:edit, log_sources:delete, log_sources:deploy |
| Source configs | source_configs:view, source_configs:create, source_configs:edit, source_configs:delete, source_configs:deploy |
| Credentials | credentials:view, credentials:create, credentials:edit, credentials:delete, credentials:use, credentials:rotate |
| Upload | upload:logs, upload:history |
| Enrichments | enrichments:view, enrichments:configure, enrichments:code, enrichments:custom:create, enrichments:custom:delete |
| Lookups | lookup:view, lookup:create, lookup:edit, lookup:delete |
| Risk | risk:view, risk:configure, risk:clear, risk:watchlists |
| Prevalence | prevalence:view, prevalence:configure, prevalence:export |
| MITRE ATT&CK | mitre:view, mitre:sync |
| pivt AI | melod:chat, melod:query, melod:parser, melod:detection, melod:summarize, melod:dashboard, melod:notebook |
| Rule repositories | rule_repositories:view, rule_repositories:manage, rule_repositories:sync, rule_repositories:import |
| Parser repositories | parser_repositories:view, parser_repositories:manage, parser_repositories:sync, parser_repositories:import |
| Playbook repositories | playbook_repositories:view, playbook_repositories:manage, playbook_repositories:sync, playbook_repositories:import |
| Detection-as-code targets | detection_code_targets:view, detection_code_targets:manage |
| Notifications | notifications:view |
| System health | system_health:view, system_health:manage |
| Settings | settings:view, settings:system, settings:retention, settings:ai, settings:webhooks, settings:ai_providers, settings:agent_models |
| Users | users:view, users:create, users:edit, users:delete |
| Groups | groups:view, groups:create, groups:edit, groups:delete |
| Roles | roles:view, roles:create, roles:edit, roles:delete |
| API keys | apikeys:view, apikeys:create, apikeys:edit, apikeys:delete |
| Sessions | sessions:admin |
| Source visibility | source_scopes:view, source_scopes:manage, source_scopes:view_all |
| Audit | audit:view |
| GDPR | gdpr:anonymize |
Notes:
credentials:useandcredentials:rotateare separate from view and edit, so a role can run a collector with a credential without being able to read or change it.risk:watchlistsis granted only to the built-in Admin role by default.source_scopes:view_allbypasses Source Visibility restrictions. Grant it sparingly.- Some areas need the matching product feature. Cases, notebooks, pivt, risk analytics, playbooks and SSO are included with nano Self-run; the open-core build doesn't include them.
API keys
API keys authenticate scripts and integrations. A key carries its own permission set, drawn from the same permissions as roles.
- The full key is shown once, at creation. nano stores only a hash and shows the key prefix afterwards.
- Keys can have an expiry date.
- Each key has a usage view.
| Action | Effect |
|---|---|
| Create, edit | Set name, permissions and expiry |
| Reset | Issues a new secret; the old one stops working |
| Disable, enable | Stops a key without deleting it, and restores it later |
| Delete | Removes the key permanently |
Practices:
- Name keys after the integration that uses them.
- Give each key only the permissions it needs, and set an expiry for temporary access.
- Rotate keys on a schedule and when someone with access leaves.
Sessions
The Sessions tab lists active sign-in sessions with user, sign-in time, last activity, IP address and user agent. Users see their own sessions. With sessions:admin you can list every session and revoke any of them, or all sessions for one user.
The defaults are a 15-minute access token, a 7-day refresh token and a 24-hour inactivity timeout.
Audit
Sign-ins, failed sign-ins, lockouts, and changes to users, groups, roles, API keys and SSO providers are written to the platform audit log. See Platform Audit.
Troubleshoot
Need help with these checks? Contact support with the request ID and time with timezone.
| Symptom | Check |
|---|---|
| User can't sign in | Status in Users (locked or disabled). |
403 on an action | The user's groups and those groups' roles. Permissions come only from group roles. |
| Search returns fewer events than expected | Source Visibility restrictions on the user's groups. |
| API call fails with a valid key | Key expiry, revocation, and whether the key has the needed permission. |