Start here
Four pages, in order. After them the manager is running and watching real devices.
Installation
Docker, Docker Compose, or as a MikroTik Container App on RouterOS. Environment variables, updating, HTTPS.
Getting Started
From your first login to your first device: sites, the RouterOS account to create, and which connection method to pick.
Dashboard and Sites
What each status tile counts, why offline and not accessible are different faults, stale rows, the task tray, and what a site is actually for.
Users and Access
The four roles, per-site scope, two-factor authentication and passkeys, and how to recover a locked-out account.
Day to day
One page per screen you will actually live in.
The Device Page
A tour of one router: traffic history and SFP optics, the DHCP pool bar, the PoE budget, LTE and SMS, BGP history — and why a tab is missing.
VLAN Editor
Describing VLANs and port roles on a live switch: the three hardware schemes, the preview, and the rollback the device runs on its own if you do not confirm.
Commands and Templates
Running one command on forty routers, picking targets by tag, per-run credentials, and templates that either execute or install as a script.
Upgrades
Checking RouterOS and firmware, the four actions, changing the update channel, and the sequential queue that upgrades powered devices before the switch feeding them.
Backups
What a backup is here, completeness checks, three levels of schedule inheritance — and why there is no restore button.
Logs
The built-in syslog receiver, what to configure on the router, and how a message is matched to its device.
Topology
How the map is built from neighbour discovery, what the dashed nodes are, and what to check when a site shows no links.
Webhooks
The fifteen events, the four body formats, scoping to sites or tags, and holding an offline alert until a flap has settled.
Security
CVE matching against the NVD feed, patch gaps read from MikroTik's own changelogs, syslog-driven auto-blocking, and the GeoIP rule generator.
Administration
Running the manager itself, and wiring it to something else.
API
Connecting a ticket system or a script: signing in with an API key, finding a device by name, and reading its state and logs.
Administration
Scanning a range for routers, the audit trail and what lands in it, and how a setting resolves between an environment variable, the database and the default.
Troubleshooting
What the status badges actually mean, reverse proxy and WebSocket, certificates, and why a tab is empty.
What this covers
These pages are about operating MikroTik Manager: getting it talking to your routers, and understanding what it tells you. They are not a RouterOS tutorial — where RouterOS itself is the subject, the authority is manual.mikrotik.com, and this documentation links there rather than paraphrasing it.
Everything here is checked against the shipped version. If a page contradicts what you see in the interface, the interface is right and the page is a bug worth reporting.
Reference material
Material that lives elsewhere and is not repeated here:
- Prometheus and Grafana — the metrics export, and a starter dashboard
- Zabbix template — monitors the manager and, through it, every device it polls
- Security — what the manager stores, encrypts and sends outbound
- Roadmap — what is planned and what has shipped
- A REST API drives the interface itself and is what the Zabbix template reads. A reference page for it is not published here yet — ask if you need one before it appears