01 / DOCUMENTATION CONTINUITY
Find a change within the right scope
History is available in client, location and device contexts. Full-text search includes earlier values and cable endpoints. Date, author, area and operation filters help narrow a long list to a specific event.
Private history profiles save filters, dates and PDF detail level. Use them for repeated reviews such as cabling changes in a server room. Dates retain an exact range, so check them before producing the next report.
02 / DOCUMENTATION CONTINUITY
Review the sequence of work
The interactive timeline displays changes and groups nearby events. Zoom, pan and open details; icons and a legend distinguish documentation areas.
The visible timeline interval is a viewing aid. Filters determine the complete result set used by the list and export; panning does not limit a report to the portion currently on screen. This supports detailed analysis without losing the wider scope.
03 / DOCUMENTATION CONTINUITY
Read the old and new values
Event details show the object, author, timestamp and changed fields before and after. In the demonstration, firmware and a PoE budget were added to a switch; both values are visible independently of its current record.
History also helps retain the context of moves and endpoint changes. Older events may not include every association available today: completeness depends on what was recorded when the operation took place.
04 / DOCUMENTATION CONTINUITY
Connect responsibility with change information
Assign a caretaker to an asset, and let users enable relevant notifications in their account settings. Application configuration supports email and signed webhooks, with delivery history and retries.
A caretaker assignment does not grant client access. Permissions and responsibility remain separate decisions. Notifications describe documentation events and require configured delivery channels and running delivery processes.
Practical workflow
Review documentation after a maintenance window
- Choose dates and relevant mounting, port and connection areas.
- Review event order and compare before-and-after values.
- Export the results and clarify changes that need more documentation.
History records documentation operations, not physical device activity. Change notifications are not availability or performance monitoring alerts.
Screenshots come from the working RackDocs application and show a demonstration environment with fictional infrastructure. They include selected views and screen details; the application is evolving. Screenshots retain the Polish interface in this English guide.