NetLock RMMNetLock RMM Docs
V — Appendix

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 Acme selected sees and acts on devices, tickets, and events scoped to Acme alone. 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_departments is 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_console is a sub-permission. The System settings group is unlocked by settings_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_enabled has 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: the Enable AI Features master switch and the ten per-feature toggles under Settings → AI / LLM. The one AI flag that is enforced per user is ai_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_panels plus 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

FlagGates
dashboard_enabledAccess to the Dashboard page and the Panel Builder.
dashboard_sql_panelsCreate and change panels with their own SQL statement. Takes effect only for accounts assigned to every tenant, and only while SQL access is configured.

See Chapter 2 — Dashboard.

X.2.3 Devices

FlagGates
devices_authorized_enabledThe main Devices list and device detail view.
devices_generalThe General tab on the device detail.
devices_softwareThe Software tab on the device detail.
devices_task_managerThe Task Manager tab.
devices_antivirusThe Antivirus tab (Windows Defender).
devices_eventsThe Events tab on the device detail.
devices_updatesThe Updates tab on the device detail.
devices_remote_shellThe Remote Shell action.
devices_remote_file_browserThe 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_controlRemote 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_locateLocate and Ring for Android devices: request the position of the device and let it ring.
devices_mobile_messageSend message for Android devices: a message that is shown on the device.
devices_remote_chatEnd 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_callAudio 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_viewerThe Remote Event Log viewer (Windows only).
devices_remote_registry_editorThe Registry Editor (Windows only).
devices_snmp_toolsThe SNMP Tools dialog.
devices_shutdownThe Shutdown command.
devices_rebootThe Reboot command.
devices_wake_on_lanWake on LAN.
devices_force_syncThe Force Sync action.
devices_usb_learningRe-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_deauthorizeThe Deauthorize action: removes the device and returns its Agent to the Unauthorized queue.
devices_moveMove a device between tenants, locations, or groups.
devices_unauthorized_enabledThe Unauthorized Devices list at /unauthorized_devices.
devices_unauthorized_authorizeThe actions that authorise a pending device or adopt it as the reinstall of an existing device of the same name.
devices_security_incidents_viewThe 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_manageAcknowledge 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_enabledThe Device World Map.
devices_topology_enabledThe 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

FlagGates
tenants_enabledThe Tenants list.
tenants_addCreate a tenant.
tenants_manageOpen tenant detail.
tenants_editSave tenant edits.
tenants_deleteDelete a tenant.
tenants_locations_addCreate a location.
tenants_locations_manageOpen location detail.
tenants_locations_editSave location edits.
tenants_locations_deleteDelete a location.
tenants_groups_addCreate a group.
tenants_groups_editEdit a group.
tenants_groups_deleteDelete a group.

See Chapter 4 — Tenants, Locations & Groups.

X.2.5 Automations

FlagGates
automation_enabledThe Automations page.
automation_addCreate an automation.
automation_editEdit an automation.
automation_deleteDelete an automation.

See Chapter 5 — Automations.

X.2.6 Policies

FlagGates
policies_enabledThe Policies list.
policies_addCreate a policy.
policies_manageOpen Policy Settings for editing.
policies_editSave changes in Policy Settings; set or remove the default policy on Manage Policies.
policies_deleteDelete a policy.

See Chapter 6 — Policies.

X.2.7 Patch Management

FlagGates
patch_management_enabledThe 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

FlagGates
collections_enabledThe 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.

FlagGates
collections_antivirus_controlled_folder_access_enabledAccess to the ACFA rulesets page.
collections_antivirus_controlled_folder_access_addCreate an ACFA ruleset.
collections_antivirus_controlled_folder_access_manageOpen an ACFA ruleset for viewing.
collections_antivirus_controlled_folder_access_editSave edits to an ACFA ruleset.
collections_antivirus_controlled_folder_access_deleteDelete an ACFA ruleset.
collections_antivirus_controlled_folder_access_processes_addAdd a process to an ACFA ruleset.
collections_antivirus_controlled_folder_access_processes_editEdit a process in an ACFA ruleset.
collections_antivirus_controlled_folder_access_processes_deleteRemove a process from an ACFA ruleset.

Application Control

FlagGates
collections_application_control_enabledThe rulesets page at /application_control_manage_rulesets.
collections_application_control_addCreate a ruleset.
collections_application_control_manageOpen a ruleset for viewing.
collections_application_control_editSave edits to a ruleset.
collections_application_control_deleteDelete a ruleset.
collections_application_control_rules_addAdd a rule to a ruleset.
collections_application_control_rules_editEdit an existing rule.
collections_application_control_rules_deleteDelete a rule.

See Chapter 8.6.

Device Control

FlagGates
collections_device_control_enabledThe whitelist and blocked-devices pages under /device-control.
collections_device_control_manageApprove a blocked device (globally only with access to all tenants) and switch a whitelist entry on or off.
collections_device_control_deleteDelete 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

FlagGates
collections_sensors_enabledThe Sensors page.
collections_sensors_addCreate a sensor.
collections_sensors_editEdit a sensor.
collections_sensors_deleteDelete a sensor.

See Chapter 8.3.

Scripts

FlagGates
collections_scripts_enabledThe Scripts page.
collections_scripts_addCreate a script.
collections_scripts_editEdit a script.
collections_scripts_deleteDelete a script.

See Chapter 8.1.

Jobs

FlagGates
collections_jobs_enabledThe Jobs page.
collections_jobs_addCreate a job.
collections_jobs_editEdit a job.
collections_jobs_deleteDelete a job.

See Chapter 8.2.

Custom Fields

FlagGates
collections_custom_fields_enabledThe Custom Fields page.
collections_custom_fields_addCreate a custom field definition.
collections_custom_fields_editEdit a definition.
collections_custom_fields_deleteDelete a definition.
collections_custom_fields_reveal_secretsReveal 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

FlagGates
collections_app_hub_enabledThe App Hub page.
collections_app_hub_addAdd a manual app entry.
collections_app_hub_manageEdit, delete, or refresh catalogues.
collections_app_hub_browse_wingetBrowse the Winget catalogue.
collections_app_hub_browse_flathubBrowse the Flathub catalogue.
collections_app_hub_browse_chocolateyBrowse the Chocolatey catalogue.

See Chapter 8.5.

Software Deployment

FlagGates
collections_software_deployment_enabledThe Manage Deployments page.
collections_software_deployment_viewOpen a deployment detail view.
collections_software_deployment_addCreate a deployment.
collections_software_deployment_manageCancel, retry, rename, clone, or delete a deployment.

See Chapter 8.8.

X.2.9 File Server

FlagGates
file_server_enabledThe File Server page.
file_server_addUpload a file or create a folder.
file_server_editEdit file metadata.
file_server_deleteDelete a file or a directory.
file_server_netlockAccess to the internal /netlock folder. Keep off for everyone except deployment operators.

See Chapter 9.1.

X.2.10 Relay Server

FlagGates
relay_server_enabledThe Relay Server page.
relay_server_manageThe Manage API Keys action.
relay_server_addCreate a relay session, and change the target of an existing one.
relay_server_editEdit 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_deleteClose or delete a session.
relay_web_accessThe 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

FlagGates
website_uptime_monitoring_enabledAccess 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

FlagGates
port_scanner_enabledAccess to the page and every action on it.

See Chapter 9.4.

X.2.13 Events & Audit

FlagGates
events_enabledThe Events page.
audit_enabledThe 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

FlagGates
users_enabledThe Users list.
users_addThe Add User dialog.
users_manageOpen User Settings for a user.
users_editSave changes in User Settings, including the permission matrix.
users_deleteDelete a user.

Roles

FlagGates
roles_enabledThe roles page (Users › Roles) and the Roles button of the Users list.
roles_addCreate, duplicate and import roles; Save as new role on an account.
roles_editSave a role; the change applies to every account that follows it.
roles_deleteDelete 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

FlagGates
reports_enabledThe Reports page.
reports_createCreate a report template.
reports_editEdit a template.
reports_deleteDelete a template.
reports_generateRun a one-off report generation.
reports_schedulesCreate or manage recurring report schedules.
reports_brand_templatesManage 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

FlagGates
tickets_enabledThe Tickets module: the list, the detail view, and Time Tracking.
tickets_createCreate a ticket from the UI.
tickets_editEdit ticket metadata in the Details tab.
tickets_deleteDelete a ticket (hard delete, no recycle bin).
tickets_assignChange the assignee on a ticket.
tickets_manage_departmentsManage departments.
tickets_manage_templatesManage response templates.
tickets_manage_labels_typesManage labels and issue types.
tickets_manage_customersManage customer and contact records.
tickets_manage_slaManage SLAs.
tickets_view_time_trackingThe Time Tracking view.
tickets_manage_webhooksManage per-department ticket webhooks.
tickets_view_statisticsThe Statistics view.
tickets_view_all_departmentsScope 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

FlagGates
settings_enabledThe Settings navigation entry.

Overview & Licensing (self-hosted-only pages)

FlagGates
settings_overview_enabledThe Overview page.
settings_overview_manageChange 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_enabledThe Licensing page.
settings_licensing_manageReplace 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

FlagGates
settings_system_enabledThe System settings sub-page.
settings_system_mysql_consoleThe MySQL console embedded in System settings. Narrower than settings_system_enabled; grant only to operators who truly need raw query access.
settings_sql_accessView 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_enabledThe Maintenance page.
settings_maintenance_manageCreate or edit maintenance tasks.
settings_protocols_enabledThe Logging page. See A.9.

Updates & Database

FlagGates
settings_updates_enabledThe Updates page.
settings_database_enabledThe Database management page.

See A.2 and A.3.

Security & Integration

FlagGates
settings_remote_screen_enabledThe Remote Screen defaults page.
settings_ip_whitelist_enabledThe 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_enabledThe 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_enabledThe 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_enabledThe SSO configuration page.
settings_integrations_enabledThe 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_manageConnecting, 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_manage alone.
  • 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.

See A.4, A.7 and A.14.

Customisation

FlagGates
settings_whitelabeling_enabledThe Whitelabeling page.
settings_globalization_enabledThe Globalization page.
settings_custom_fields_enabledThe Custom Fields settings page with the global custom field values; also required for the global custom field values in the public API.

See A.5, A.6, and A.12.

AI / LLM

FlagGates
settings_ai_llm_enabledThe 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

FlagGates
settings_notifications_enabledAccess to the Notifications page.

Per-channel pattern

For each channel <channel> in mail, microsoft_teams, telegram, ntfysh, webhook:

FlagGates
settings_notifications_<channel>_enabledThe channel's tab on the Notifications page.
settings_notifications_<channel>_addCreate a recipient on this channel.
settings_notifications_<channel>_testSend a test to a recipient on this channel.
settings_notifications_<channel>_editEdit a recipient on this channel.
settings_notifications_<channel>_deleteDelete a recipient on this channel.

Email extras

FlagGates
settings_notifications_mail_smtpThe 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

FlagGates
ai_enabledNo 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_enabledThe AI Chat page at /ai-chat.
enduser_ai_accountsThe 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 the collections_*_add / _edit flags, patch_management_enabled, and audit_enabled for incident review.
  • Deployment operator: L2 plus settings_*_enabled for the settings sub-pages they own, users_enabled / _add / _manage / _edit if they onboard staff, but not settings_system_mysql_console or users_delete unless strictly required.

These profiles are starting points, not fixed rules.