NetLock RMMNetLock RMM Docs
II — Console Reference

Community

Where to find Community Scripts, Community Reports, and Community Themes — and how deployment-level Members Portal authentication works.

Community

15.1 What Community means in NetLock RMM

Community is an integration layer rather than a place. It is not a standalone section in the Console navigation — there is no Community entry between Reports and Management, and no shared-intel dashboard. Instead, three feature areas each embed a small Community surface that talks to the same Members Portal: a Scripts catalogue, a Reports catalogue, and a Themes catalogue. This chapter is a short index of where each lives.

15.2 Where to find each community feature

FeatureWhere it livesFull reference
Community ScriptsScripts library (Collections)Chapter 8.1
Community ReportsReports moduleChapter 11.9
Community ThemesWhitelabeling settingsChapter A.6

Each surface offers the same four actions against its own catalogue: browse, import into your local library, publish a local item back to the community, and report an abusive or broken entry.

15.3 How community authentication works

Community features authenticate at the deployment level. The administrator stores a single Members Portal API key in the Console's settings, and every user of that deployment inherits that identity when they click a community action. End users do not sign into a separate Members Portal account, and there is no per-user community login. The Publish and Import buttons embedded in the Scripts, Reports, and Whitelabeling pages therefore work for any user who holds the parent feature's own permission flag — for example collections_scripts_enabled for Community Scripts — and become inert when the deployment has no API key configured.

15.4 A note on the Arcade

The gamepad icon in the app bar opens the Arcade, a picker with three mini games. Virus Defense is a tower defence in which security tools hold malware back; Kernel Panic is a first-person game in which an administrator clears a data center floor by floor; Overclock Rally is a racing game with a season of its own, driven on twelve circuits named after the parts of a data center. On phones the same entry sits in the overflow menu behind the three dots.

They are an Easter egg, not a product feature: there is no permission check beyond being signed in, and no route of their own — all three open as dialogs on whatever page you are on. High scores are kept in the browser that played them, per browser and per device, and are never sent to the server. The same is true of the progress Overclock Rally saves: its career, credits and best lap times live in that one browser and are gone with its site data.

The Mini game checkbox under App bar icons in the whitelabel settings hides the gamepad icon and with it all three games; see Chapter A.6.