Permission reference
Canonical list of every permission flag in NetLock RMM, grouped by feature area, with a note on what each flag gates.
Permission reference
This appendix is the canonical catalogue of every permission flag NetLock RMM exposes to role configuration. Use it as a lookup when the User Settings matrix is too dense to navigate, when you are auditing an existing user's rights, or when you are designing a new role and need to see everything the product can gate.
For how to create a user and assign these flags, see Chapter 14 — Users & Roles.
X.2.1 The access model in one page
Permissions are granted per account, directly or through a role. Three things matter before you start assigning flags.
- Roles. An account either follows a role, whose changes apply to every account that follows it, or holds custom permissions. See Chapter 14.4.
- Permissions are boolean flags. Each flag is either granted or not granted. Access control is exercised through the matrix on
User Settings, where section-level switches enable a block and child checkboxes gate finer-grained actions within the block. Turning a parent switch off disables every child regardless of the child's stored value. - Tenant scoping is layered on top. Independent of flags, every user record holds a list of tenants they may act on. A user with every flag enabled but only tenant
Acmeselected sees and acts on devices, tickets, and events scoped toAcmealone. Global pages (Settings, Events, Audit, Users, Reports library) are not tenant-scoped; feature pages that operate on devices are.
Four specific facts shape how the flags below behave:
tickets_view_all_departmentsis a scope flag, not a feature flag. Users without it still see the Tickets page, create tickets, reply, and close tickets, but only in the department(s) they are assigned to. The flag widens their view to every department; it does not gate access to the Tickets page itself.settings_system_mysql_consoleis a sub-permission. The System settings group is unlocked bysettings_system_enabled, but the MySQL console that lives inside it takes a separate, narrower flag. Keep it off unless the user truly needs raw query access.ai_enabledhas no effect. The flag is present in the matrix and stored on the user, but nothing reads it. What decides whether AI is available is deployment-wide: theEnable AI Featuresmaster switch and the ten per-feature toggles underSettings → AI / LLM. The one AI flag that is enforced per user isai_chat_page_enabled. See A.11.- Custom SQL depends on SQL access, not on a separate SQL permission. Custom SQL and the query builders in reports, dashboard panels and custom fields run only as the MySQL user configured under
Settings → SQL access(settings_sql_access). With it configured, everyone who may edit the item may use them:reports_create/reports_edit,dashboard_sql_panelsplus assignment to every tenant,collections_custom_fields_add/collections_custom_fields_edit. See A.12.
The following sections list every flag.
X.2.2 Dashboard
| Flag | Gates |
|---|---|
dashboard_enabled | Access to the Dashboard page and the Panel Builder. |
dashboard_sql_panels | Create and change panels with their own SQL statement. Takes effect only for accounts assigned to every tenant, and only while SQL access is configured. |
X.2.3 Devices
| Flag | Gates |
|---|---|
devices_authorized_enabled | The main Devices list and device detail view. |
devices_general | The General tab on the device detail. |
devices_software | The Software tab on the device detail. |
devices_task_manager | The Task Manager tab. |
devices_antivirus | The Antivirus tab (Windows Defender). |
devices_events | The Events tab on the device detail. |
devices_updates | The Updates tab on the device detail. |
devices_remote_shell | The Remote Shell action. |
devices_remote_file_browser | The File Browser action, and pasting files into a remote screen session from the web console or the Relay App. The server checks it for every paste of every viewer; for the Relay App it is checked on the account that owns the relay key (A.7.10). |
devices_remote_control | Remote screen control in the web console, and in the Relay App and the NetLock app for the account that owns the relay key (together with the key's Screen control switch under Relay Server → Manage API Keys). Covers starting and stopping a recording and viewing the remote clipboard (A.7.9). Also viewing and, when the device's policy allows it, controlling the screen of Android devices from the web console (A.7.12). |
devices_mobile_locate | Locate and Ring for Android devices: request the position of the device and let it ring. |
devices_mobile_message | Send message for Android devices: a message that is shown on the device. |
devices_remote_chat | End user chat: the chat with the signed-in user of a device from the device page and the remote control dialog, and the chat requests end users start from the tray icon (badge and list in the header of the console). Accounts and roles that held devices_remote_control received it once with the update to 3.3.0.5. |
devices_remote_audio_call | Audio call: the voice call with the signed-in user of a Windows device from the end user chat and the remote control dialog (A.7.7). Members of the built-in Administrator role hold it automatically; other accounts and roles start without it. |
devices_remote_eventlog_viewer | The Remote Event Log viewer (Windows only). |
devices_remote_registry_editor | The Registry Editor (Windows only). |
devices_snmp_tools | The SNMP Tools dialog. |
devices_shutdown | The Shutdown command. |
devices_reboot | The Reboot command. |
devices_wake_on_lan | Wake on LAN. |
devices_force_sync | The Force Sync action. |
devices_usb_learning | Re-learn connected devices and End learning now on the USB Devices tab (Chapter 3.3), and the bulk re-learn on the Whitelist tab of Device Control (Chapter 8.7). Part of the built-in Administrator role and the Technician template; not in the Helpdesk, Read-only and Reporting templates. Custom roles get it when an administrator adds it. |
devices_deauthorize | The Deauthorize action: removes the device and returns its Agent to the Unauthorized queue. |
devices_move | Move a device between tenants, locations, or groups. |
devices_unauthorized_enabled | The Unauthorized Devices list at /unauthorized_devices. |
devices_unauthorized_authorize | The actions that authorise a pending device or adopt it as the reinstall of an existing device of the same name. |
devices_security_incidents_view | The security incident dialog of a device on /devices and /unauthorized_devices, with the JSON export (see 3.8). The red row and the chip are shown without it. Accounts and roles that held devices_general or devices_unauthorized_enabled received it once with the update. |
devices_security_incidents_manage | Acknowledge security incidents, whitelist a device, release an isolated unauthorized device for analysis, release an isolation and block new registrations of the installer package; revoking the package additionally needs agent_installers_enabled. Accounts and roles that held devices_unauthorized_authorize received it once with the update. The Read only template does not include it. |
devices_world_map_enabled | The Device World Map. |
devices_topology_enabled | The Device Topology map at /device-topology: tenants, locations, inferred subnets and the devices attached to them. Each user keeps their own node arrangement. |
See Chapter 3 — Devices.
X.2.4 Tenants, Locations & Groups
| Flag | Gates |
|---|---|
tenants_enabled | The Tenants list. |
tenants_add | Create a tenant. |
tenants_manage | Open tenant detail. |
tenants_edit | Save tenant edits. |
tenants_delete | Delete a tenant. |
tenants_locations_add | Create a location. |
tenants_locations_manage | Open location detail. |
tenants_locations_edit | Save location edits. |
tenants_locations_delete | Delete a location. |
tenants_groups_add | Create a group. |
tenants_groups_edit | Edit a group. |
tenants_groups_delete | Delete a group. |
See Chapter 4 — Tenants, Locations & Groups.
X.2.5 Automations
| Flag | Gates |
|---|---|
automation_enabled | The Automations page. |
automation_add | Create an automation. |
automation_edit | Edit an automation. |
automation_delete | Delete an automation. |
X.2.6 Policies
| Flag | Gates |
|---|---|
policies_enabled | The Policies list. |
policies_add | Create a policy. |
policies_manage | Open Policy Settings for editing. |
policies_edit | Save changes in Policy Settings; set or remove the default policy on Manage Policies. |
policies_delete | Delete a policy. |
See Chapter 6 — Policies.
X.2.7 Patch Management
| Flag | Gates |
|---|---|
patch_management_enabled | The Patch Management page with all its tabs. |
The page enables or disables as a whole; there is no per-tab flag. See Chapter 7 — Patch Management.
X.2.8 Collections
Master switch
| Flag | Gates |
|---|---|
collections_enabled | The top-level Collections navigation group. Every sub-feature below requires this flag and its own flag. |
Antivirus Controlled Folder Access
Controlled Folder Access rulesets are managed through the Public API (see X.9); the Console has no menu entry for them.
| Flag | Gates |
|---|---|
collections_antivirus_controlled_folder_access_enabled | Access to the ACFA rulesets page. |
collections_antivirus_controlled_folder_access_add | Create an ACFA ruleset. |
collections_antivirus_controlled_folder_access_manage | Open an ACFA ruleset for viewing. |
collections_antivirus_controlled_folder_access_edit | Save edits to an ACFA ruleset. |
collections_antivirus_controlled_folder_access_delete | Delete an ACFA ruleset. |
collections_antivirus_controlled_folder_access_processes_add | Add a process to an ACFA ruleset. |
collections_antivirus_controlled_folder_access_processes_edit | Edit a process in an ACFA ruleset. |
collections_antivirus_controlled_folder_access_processes_delete | Remove a process from an ACFA ruleset. |
Application Control
| Flag | Gates |
|---|---|
collections_application_control_enabled | The rulesets page at /application_control_manage_rulesets. |
collections_application_control_add | Create a ruleset. |
collections_application_control_manage | Open a ruleset for viewing. |
collections_application_control_edit | Save edits to a ruleset. |
collections_application_control_delete | Delete a ruleset. |
collections_application_control_rules_add | Add a rule to a ruleset. |
collections_application_control_rules_edit | Edit an existing rule. |
collections_application_control_rules_delete | Delete a rule. |
See Chapter 8.6.
Device Control
| Flag | Gates |
|---|---|
collections_device_control_enabled | The whitelist and blocked-devices pages under /device-control. |
collections_device_control_manage | Approve a blocked device (globally only with access to all tenants) and switch a whitelist entry on or off. |
collections_device_control_delete | Delete whitelist entries and dismiss blocked devices. |
There is no _add flag. An administrator adds an entry through the approval flow on Blocked Devices, which is gated by the _manage flag plus the ability to act on the specific scope. Devices also add device-scoped entries themselves while they learn; re-learning is gated by devices_usb_learning in the Devices group. See Chapter 8.7.
Sensors
| Flag | Gates |
|---|---|
collections_sensors_enabled | The Sensors page. |
collections_sensors_add | Create a sensor. |
collections_sensors_edit | Edit a sensor. |
collections_sensors_delete | Delete a sensor. |
See Chapter 8.3.
Scripts
| Flag | Gates |
|---|---|
collections_scripts_enabled | The Scripts page. |
collections_scripts_add | Create a script. |
collections_scripts_edit | Edit a script. |
collections_scripts_delete | Delete a script. |
See Chapter 8.1.
Jobs
| Flag | Gates |
|---|---|
collections_jobs_enabled | The Jobs page. |
collections_jobs_add | Create a job. |
collections_jobs_edit | Edit a job. |
collections_jobs_delete | Delete a job. |
See Chapter 8.2.
Custom Fields
| Flag | Gates |
|---|---|
collections_custom_fields_enabled | The Custom Fields page. |
collections_custom_fields_add | Create a custom field definition. |
collections_custom_fields_edit | Edit a definition. |
collections_custom_fields_delete | Delete a definition. |
collections_custom_fields_reveal_secrets | Reveal the stored value of a Secret custom field on a device or on tenant, location, group or global level. Every reveal is written to the audit log. Not granted by default; administrator accounts hold it. |
collections_custom_fields_edit also gates changing values on devices and on tenant, location and group level; the global level needs settings_custom_fields_enabled in addition. See Chapter 8.4.
App Hub
| Flag | Gates |
|---|---|
collections_app_hub_enabled | The App Hub page. |
collections_app_hub_add | Add a manual app entry. |
collections_app_hub_manage | Edit, delete, or refresh catalogues. |
collections_app_hub_browse_winget | Browse the Winget catalogue. |
collections_app_hub_browse_flathub | Browse the Flathub catalogue. |
collections_app_hub_browse_chocolatey | Browse the Chocolatey catalogue. |
See Chapter 8.5.
Software Deployment
| Flag | Gates |
|---|---|
collections_software_deployment_enabled | The Manage Deployments page. |
collections_software_deployment_view | Open a deployment detail view. |
collections_software_deployment_add | Create a deployment. |
collections_software_deployment_manage | Cancel, retry, rename, clone, or delete a deployment. |
See Chapter 8.8.
X.2.9 File Server
| Flag | Gates |
|---|---|
file_server_enabled | The File Server page. |
file_server_add | Upload a file or create a folder. |
file_server_edit | Edit file metadata. |
file_server_delete | Delete a file or a directory. |
file_server_netlock | Access to the internal /netlock folder. Keep off for everyone except deployment operators. |
See Chapter 9.1.
X.2.10 Relay Server
| Flag | Gates |
|---|---|
relay_server_enabled | The Relay Server page. |
relay_server_manage | The Manage API Keys action. |
relay_server_add | Create a relay session, and change the target of an existing one. |
relay_server_edit | Edit a relay session and turn it on or off. Changing its target device, remote host, port or protocol also needs relay_server_add. |
relay_server_delete | Close or delete a session. |
relay_web_access | The Web interface action on the Devices page: open the web interface of a device, or of a host the device can reach, in a browser tab through a temporary relay session. Accounts that held relay_server_add received it once with the update. |
See Chapter 9.2.
X.2.11 Website Uptime Monitoring
| Flag | Gates |
|---|---|
website_uptime_monitoring_enabled | Access to the page. |
The page has a single access flag, which also controls the add, edit, and delete buttons on the page. See Chapter 9.3.
X.2.12 Port Scanner
| Flag | Gates |
|---|---|
port_scanner_enabled | Access to the page and every action on it. |
See Chapter 9.4.
X.2.13 Events & Audit
| Flag | Gates |
|---|---|
events_enabled | The Events page. |
audit_enabled | The Audit page. |
The two flags are independent. Most operators need events_enabled; audit_enabled is usually reserved for security and compliance roles. See Chapter 12 — Events & Audit.
X.2.14 Users
| Flag | Gates |
|---|---|
users_enabled | The Users list. |
users_add | The Add User dialog. |
users_manage | Open User Settings for a user. |
users_edit | Save changes in User Settings, including the permission matrix. |
users_delete | Delete a user. |
Roles
| Flag | Gates |
|---|---|
roles_enabled | The roles page (Users › Roles) and the Roles button of the Users list. |
roles_add | Create, duplicate and import roles; Save as new role on an account. |
roles_edit | Save a role; the change applies to every account that follows it. |
roles_delete | Delete a role that no account follows. |
A user who holds users_edit can edit every other user's permission flags and role, including their own. Grant this flag only to accounts that should have full administrative rights. The console enforces one limit: the last enabled account holding users_enabled, users_manage and users_edit keeps them and stays enabled. Binding an account to a role is a users_edit action; changing the role itself, which reaches every account that follows it, is roles_edit. See Chapter 14 — Users & Roles.
X.2.15 Reports
| Flag | Gates |
|---|---|
reports_enabled | The Reports page. |
reports_create | Create a report template. |
reports_edit | Edit a template. |
reports_delete | Delete a template. |
reports_generate | Run a one-off report generation. |
reports_schedules | Create or manage recurring report schedules. |
reports_brand_templates | Manage brand templates on the Brands tab. |
Custom SQL and the Visual Query Builder in report widgets additionally need SQL access (Settings → SQL access, see settings_sql_access in X.2.17). See Chapter 11 — Reports.
X.2.16 Tickets
| Flag | Gates |
|---|---|
tickets_enabled | The Tickets module: the list, the detail view, and Time Tracking. |
tickets_create | Create a ticket from the UI. |
tickets_edit | Edit ticket metadata in the Details tab. |
tickets_delete | Delete a ticket (hard delete, no recycle bin). |
tickets_assign | Change the assignee on a ticket. |
tickets_manage_departments | Manage departments. |
tickets_manage_templates | Manage response templates. |
tickets_manage_labels_types | Manage labels and issue types. |
tickets_manage_customers | Manage customer and contact records. |
tickets_manage_sla | Manage SLAs. |
tickets_view_time_tracking | The Time Tracking view. |
tickets_manage_webhooks | Manage per-department ticket webhooks. |
tickets_view_statistics | The Statistics view. |
tickets_view_all_departments | Scope flag. Widens the operator's view to every department. Without it, the operator sees only tickets on the department(s) they are assigned to. |
See Chapter 10 — Tickets.
X.2.17 Settings
Every flag below gates a specific Settings sub-page. The top-level Settings nav group requires settings_enabled; each sub-page requires its own flag in addition.
Access to the Settings group
| Flag | Gates |
|---|---|
settings_enabled | The Settings navigation entry. |
Overview & Licensing (self-hosted-only pages)
| Flag | Gates |
|---|---|
settings_overview_enabled | The Overview page. |
settings_overview_manage | Change the storage limit and the public backend URL on the Overview page. A new URL becomes active after the web console and the server have been restarted. |
settings_licensing_enabled | The Licensing page. |
settings_licensing_manage | Replace the Members Portal API key on the Licensing page. The new key becomes active after the web console and the server have been restarted. |
See A.1.
System & Maintenance
| Flag | Gates |
|---|---|
settings_system_enabled | The System settings sub-page. |
settings_system_mysql_console | The MySQL console embedded in System settings. Narrower than settings_system_enabled; grant only to operators who truly need raw query access. |
settings_sql_access | View and change Settings → SQL access, the MySQL user that custom SQL in reports, dashboards and custom fields runs as. The Administrator role has it; accounts and custom roles that held settings_reports_enabled or settings_dashboards_enabled received it once with the update to 3.3.0.11. The Technician and read-only templates do not include it. See A.12.1. |
settings_maintenance_enabled | The Maintenance page. |
settings_maintenance_manage | Create or edit maintenance tasks. |
settings_protocols_enabled | The Logging page. See A.9. |
Updates & Database
| Flag | Gates |
|---|---|
settings_updates_enabled | The Updates page. |
settings_database_enabled | The Database management page. |
Security & Integration
| Flag | Gates |
|---|---|
settings_remote_screen_enabled | The Remote Screen defaults page. |
settings_ip_whitelist_enabled | The tabs IP whitelist and Country restriction of the Security page, i.e. the IP whitelist of the web console and the country restriction of the web console and the server (see A.4.1a). |
settings_sessions_enabled | The tab Sessions of the Security page: idle timeout, maximum lifetime and Stay signed in of Web Console sign-ins (see A.4.1c). |
settings_rate_limiting_enabled | The tabs Rate limiting and Security incidents of the Security page: mode, limits, blocks, exemptions (see A.4.1b), and the two switches of the security incident detection (see 3.8). Accounts and roles that held settings_ip_whitelist_enabled received it once with the update; the Technician template does not include it. |
settings_sso_enabled | The SSO configuration page. |
settings_integrations_enabled | The Integrations store, connections, their mappings, history and log. Read only, and the role template Read only includes it. No lists are read from a vendor with this flag alone. |
settings_integrations_manage | Connecting, testing, replacing credentials, settings, pausing, disconnecting and deleting connections, mappings, auto mapping, the company import and debug logging of a connection. |
The tenant scope of an account limits these two flags only where tenant data is touched:
- Connecting, credentials, settings, pausing and disconnecting need
settings_integrations_managealone. - Mappings of tenants and locations outside the scope are locked and show no names.
- Auto mapping and the company import offer only tenants in scope.
- History and log lines of other tenants are hidden.
Creating tenants in the import additionally needs tenants_add, and switching on the public API from the store needs settings_api_tokens_manage. The full table is in A.14.7.
Customisation
| Flag | Gates |
|---|---|
settings_whitelabeling_enabled | The Whitelabeling page. |
settings_globalization_enabled | The Globalization page. |
settings_custom_fields_enabled | The Custom Fields settings page with the global custom field values; also required for the global custom field values in the public API. |
AI / LLM
| Flag | Gates |
|---|---|
settings_ai_llm_enabled | The AI / LLM configuration page. |
See A.11.
X.2.18 Notifications
The Notifications page has one master flag and five per-channel flag groups. Every channel follows the same pattern, with Email adding one extra flag for SMTP.
Master
| Flag | Gates |
|---|---|
settings_notifications_enabled | Access to the Notifications page. |
Per-channel pattern
For each channel <channel> in mail, microsoft_teams, telegram, ntfysh, webhook:
| Flag | Gates |
|---|---|
settings_notifications_<channel>_enabled | The channel's tab on the Notifications page. |
settings_notifications_<channel>_add | Create a recipient on this channel. |
settings_notifications_<channel>_test | Send a test to a recipient on this channel. |
settings_notifications_<channel>_edit | Edit a recipient on this channel. |
settings_notifications_<channel>_delete | Delete a recipient on this channel. |
Email extras
| Flag | Gates |
|---|---|
settings_notifications_mail_smtp | The deployment-wide SMTP configuration dialog. Separate from mail_edit: a user can manage recipients without being granted the ability to change the global SMTP server. |
See A.8.
X.2.19 AI
| Flag | Gates |
|---|---|
ai_enabled | No effect; the flag is only stored on the user. AI availability is decided deployment-wide under Settings → AI / LLM; see A.11.1. |
ai_chat_page_enabled | The AI Chat page at /ai-chat. |
enduser_ai_accounts | The Customer AI dialog for managing end-user AI chat accounts: activation, per-user and per-tenant token limits, auto-activation, and statistics. Opened from the Tenants list and from tenant detail; scoped to the operator's tenants. See Chapter 13.6. |
The individual AI features (script analysis, remote shell, event analysis, sensor and job creation, event-log analysis, ticket analysis, audit analysis, the Automations assistant, the operator AI Chat, and the end-user tray chat) are switched on at the deployment level under Settings → AI / LLM, not per user. The AI Chat page is gated on both levels: the deployment toggle decides whether it exists at all, ai_chat_page_enabled decides who may open it. See Chapter 13 and A.11.4.
X.2.20 Designing a role
Roles are stored objects; see Chapter 14.4 for the roles page and the Start from templates (Technician, Helpdesk, Read-only, Reporting). The templates cover the common cases; the profiles below describe what such a role typically holds and where a deployment usually adds to or takes from a template:
- Read-only observer:
dashboard_enabled,devices_authorized_enabled,devices_general,events_enabled,reports_enabled,reports_generate. - Level-1 technician: observer plus
devices_remote_shell,devices_remote_file_browser,devices_remote_control,devices_remote_chat,devices_reboot,devices_force_sync,collections_enabled,collections_scripts_enabled,tickets_enabled,tickets_create,tickets_edit. - Level-2 engineer: L1 plus the
policies_*flags,automation_*, most of thecollections_*_add/_editflags,patch_management_enabled, andaudit_enabledfor incident review. - Deployment operator: L2 plus
settings_*_enabledfor the settings sub-pages they own,users_enabled/_add/_manage/_editif they onboard staff, but notsettings_system_mysql_consoleorusers_deleteunless strictly required.
These profiles are starting points, not fixed rules.