IT Glue Documents — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited IT Glue Documents (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Documents in IT Glue provide structured documentation storage for organizations, enabling technicians to create runbooks, procedures, network diagrams, and general documentation. Documents support rich HTML content, embedded passwords, and relationships to other IT Glue resources.
records are flexible assets, not free-form documents; use itglue-flexible-assets.
records that documents embed by reference; use itglue-passwords.
itglue-configurations.
Documents consist of:
Folders provide hierarchical organization:
Organization: Acme Corporation
└── Documents
├── Onboarding
│ ├── New User Setup
│ └── Hardware Deployment
├── Procedures
│ ├── Backup Procedures
│ └── Disaster Recovery
└── Network
├── Network Diagram
└── IP SchemeDocuments can embed:
<div data-embedded-password-id="12345"></div>)<div data-embedded-configuration-id="67890"></div>)<img src="/uploads/organization/123/...">)Multi-section documents are composed of ordered sections rather than a single content blob — this is what the Document Sections API reads and writes.
| Type | Description |
|---|---|
Document::Heading | Heading element (renders as <h2>, etc.) |
Document::Text | Rich HTML text block |
See references/fields.md for the complete field reference.
Sections must be replaced, not patched, and the document must be republished for changes to appear:
GET .../relationships/sections)See references/examples.md for the full restructureDocument implementation, plus runbook creation, search, export, health-check, and template-cloning workflow examples.
Ensure the target folder exists, build HTML content section by section (overview, prerequisites, steps, embedded credentials), create the document, then create related items linking it to relevant configurations.
GET /documents (top-level) returns 404 in practice. Use GET /organizations/:id/relationships/documents instead.PATCH /documents/:id with a content attribute silently does nothing on multi-section documents. Use the Document Sections API (create/update/delete individual sections) instead.PATCH /documents/:id/publish makes section edits visible. POST returns 404; no request body is required.See references/api.md for the complete endpoint catalog: document, section, folder, and related-item CRUD with full request/response examples.
search_flexible_assets, since flexible assets are the more common documentation mechanism in practice.PATCH /documents/:id — the top-level content attribute is only honored for single-blob (non-sectioned) documents./documents/:id/publish returns 404.See references/errors.md for the complete error-code and validation-error tables plus a retry pattern for invalid-folder errors.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.