NetLock RMM DocsCommunity
Where to find Community Scripts, Community Reports, and Community Themes — and how deployment-level Members Portal authentication works.
Community
Optional module: Community features require a valid Members Portal API key configured on the deployment. Without it, the publish and import buttons on feature pages remain disabled.
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
| Feature | Where it lives | Full reference |
|---|---|---|
| Community Scripts | Scripts library (Collections) | Chapter 8.1 |
| Community Reports | Reports module | Chapter 11.9 |
| Community Themes | Whitelabeling settings | Chapter 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 Virus Defense Easter egg
The route /community/events/retro renders a small retro tower-defense game called Virus Defense. It is an Easter egg, not a product feature, and has no permission check. You can disable it in the whitelabel section.
Related chapters
- Chapter 8.1 — Scripts — Community Scripts browser, publish, and report flows.
- Chapter 11.9 — Community Reports — Community Reports browser and publish flow.
- Chapter A.6 — Whitelabeling & themes — Community Themes browser, import, and publish flow.