IT documentation that lives where the work happens, not in a wiki nobody opens

Every MSP has a documentation tool, and every MSP has techs who don't open it during an actual incident, because pulling up a separate app, searching for the right client, and finding the right article costs more time than just solving the problem from memory (or from a guess). The documentation isn't bad. It's just filed in a place that isn't where the work happens.

IT documentation in Nexus is attached to the records it actually describes — a device, a client, a site — instead of living in a parallel system a tech has to remember to cross-reference. Network diagrams, runbooks, and client-specific procedures surface from the same place a ticket, an alert, or a device history already opens.

Why attachment beats a separate wiki

• A tech working a ticket sees the relevant documentation without a second search — it's already linked to the device or client the ticket is about.
• Documentation that's attached to a record gets updated when the record does, instead of drifting out of sync in a wiki nobody remembers to revisit.
• Onboarding a new tech is faster when "where do I find the network layout for this client" has one obvious answer, not "check the wiki, or the shared drive, or ask someone."

This is a smaller, quieter capability than the AI layer or the security suite, and that's exactly why it tends to get left off feature-comparison tables — but it's one of the places where "one platform instead of a stitched stack" pays off in minutes saved every single day, not just in fewer invoices.