Documentation

RabbitRMM documentation

Everything from your first sign-in to running patch rings across hundreds of clients. Start with the setup guide; come back to the user guide when you want the detail.

Five ideas the whole product rests on

Clients

Every device, person, policy override, network and report belongs to a client: one of the organisations you support. In code and APIs you may see the word tenant; in the portal it is always Client.

Global, client and filter scope

Policies, scripts and tags can be global (every client, including ones you add later), belong to one client, or target a filter such as device type, operating system, RAM, manufacturer or tag. Global policies can exclude named clients.

Roles

A role is a set of permissions plus the clients it applies to. A person can hold several roles and switch between them; menus and buttons only appear for what the current role allows.

Tags

Tags come from a shared library (global or per client). They drive configuration profiles, onboarding, policy filters and reports, so naming them consistently pays off.

The agent

A small Windows service that talks to RabbitRMM over outbound HTTPS only. It reports inventory and health, installs updates and apps, runs scripts, carries remote sessions and can act as its client's network collector.

Keyboard tip

Press / anywhere in the portal to search clients, devices and people.