Write and share field guides
Write field guides as shared pages with fields filled in for each device, link them to models so they appear beside outages, and keep every version.
GuideReviewed against the application source on October 12, 2026
Guides are shared pages
Knowledge › Guides holds your team’s field guides as shared pages laid out like these docs. Anyone with editing rights can change a guide; Cenovel keeps every version. The page lists guides By category or Recently edited. It is behind Field guides in Features.
Write a guide
- Choose New guide, give it a title and a category (Hardware and replacement, New installs and cabling, Troubleshooting, Procedures and standards, or Vendor notes).
- Write. It saves as you type; the status reads Saving…, then Saved with the time.
- Use Insert for a Note, Caution, Commands, Table, Picture or Divider, a Record link that reads a site’s, closet’s, model’s, switch’s or asset’s name as it is today and opens it, or a Field: Site name, Site address, Closet, Device name, Device address, Model or Vendor, filled in for whichever device the guide is opened for.
- Choose What it’s for and pick models or equipment categories. A model’s guides then show on its device pages, on the incident page and beside its outages.
Work on one together
The page head shows who is viewing now, and a guide shows who is editing. Saves are merged part by part; if someone changed the same part, Cenovel shows both and asks you to Take their version or Keep mine. There is no live shared cursor and no comments.
History lists versions (one person’s saves within a few minutes are one version), each with View and restore.
Who can edit
By default, the members of one department edit every guide. An Administrator EX sets it in Department that edits guides, in Settings › System › Deployment, under Everyday work; blank lets anyone allowed to edit the Guides page. Give one person every guide with a person rule on Guides in Settings › People and access, or one guide with Who can edit on that guide.
Pictures and Resources files are scanned for malware like every upload. Header search looks inside guides and resources.
See also: Permissions and departments
Describes the release being prepared for deployment. Check the behavior on your installed release.