Hi everyone,
This is one of the projects we’ve been working on behind the scenes, with Design, Knowledge Management, Product, and Product Marketing all pitching in. We’re super excited to finally share the all-new Atera Help Center with you.
If you joined the Q3 2026 Product Updates webinar, this was the “one more thing” I showed at the end. It’s now available to everyone.
We looked at the guides people use most and what we’ve shipped recently to decide what to feature in each section. We also rewrote the descriptions so you can tell what each article helps you do before opening it.
Find the article by topic
The new left-hand menu lets you expand a topic, browse its subcategories, and see the articles inside. If you’re trying to figure out why a patch failed, for example, you can go to RMM >> Patch management and find the guide from there.
Inside an article, On this page takes you straight to the section you need. Where a guide covers both audiences, you can switch between MSP and IT Department instructions. Explore the Help Center
See what to do before and after a setup step
One thing I wanted to improve was what happens when you land halfway through a setup from a search result. It should be easy to see what you need in place first, where you are in the setup, and what to do next.
You can see the first version of this in the Robin articles today. The menu takes you from getting started and preparing your environment through setup, configuration, and measuring results. At the bottom of a Robin article, look for Related journey articles, just below the Related articles list. Use the arrows to browse the cards and open an earlier guide or move on to the next one. We’re working on bringing that same structure to more areas of the Help Center. Explore the Robin guides
Open, copy, or download an article as Markdown
Go to Article actions → View as Markdown. You can read the Markdown right in your browser, use Copy to grab the text, or choose Download to save a .md file.
Markdown keeps headings, steps, and links in a plain-text format that tools can parse. You can bring an article into your team’s searchable documentation, use it as a starting point for an internal runbook, or give it to an AI assistant as source material. For example, you could ask your assistant to pull the prerequisites out of a setup guide and turn them into a checklist for your rollout. Try it on the Patch Management Dashboard article
Take a look at the new Help Center and let us know how it works for you. If there’s a setup where you still find yourself opening three articles to figure out where to start, tell me which one. That’s the kind of feedback I’d like us to use as we build out the next journeys.
++
Dima L
Technical Product Marketing Manager
Atera