IT Glue documentation: MSP procedures versus client secrets

IT Glue-style documentation platforms hold two things that must never be mixed: an MSP's own runbooks, SOPs and process history, and client credentials and environment details. Client secrets are never in scope. An MSP's own procedure history could support a SourceX review if the firm meets the size and rights baseline.

What does an IT documentation platform hold?

An MSP documentation platform such as IT Glue is where technicians keep how-to articles, runbooks, onboarding checklists, asset records, network notes and password references for each client. It is read constantly and updated after incidents.

That makes it one of the richest sources of procedural knowledge in an MSP, and one of the most sensitive. The line between the MSP's method and the client's environment is the whole subject of this page.

Which parts are the MSP's and which are the client's?

ContentBelongs toIn scope for a licensing review?
Generic runbooks and troubleshooting proceduresThe MSPPotentially, after review
Onboarding and offboarding checklists (templates)The MSPPotentially
Documentation revision history and who changed whatThe MSPPotentially, with names handled per agreed rules
Client-specific network diagrams and configurationsThe clientNo
Credentials, vault entries, MFA recovery dataThe clientNever
Client contacts, licenses, contractsThe clientNo

If you remember one rule, make it this: credentials and environment details are never in scope. No procedure is worth putting a client at risk.

Why would a procedure history matter to AI buyers?

AI is shifting from models that answer questions to agents that perform tasks. Agents that handle IT operations need examples of how a procedure is written, followed, corrected and retired. A documentation platform with years of revisions shows that cycle, which is rare on the public web.

See AI agents in IT service management for the broader picture. Documentation context is most useful alongside ticket history, as in the HaloPSA brief.

What do MSPs usually need to sort out first?

  1. Separate template articles from client-specific ones, using the platform's own structure.
  2. Identify who owns the documentation program and who can authorize a review.
  3. Check client contracts for clauses about documentation ownership and confidentiality.
  4. Confirm that no secrets sit inside free-text articles, which is common.
  5. Agree redaction rules with SourceX before any work begins, if the MSP proceeds.

The question on sharing client data goes deeper on the permission side.

How does a partner spot a documentation-mature MSP?

  • 50+ full-time employees at peak (contractors excluded)
  • Documentation practice running for several years, with revision history intact
  • Templates and standards separate from client records
  • A named person who maintains the knowledge base
  • Records elsewhere too (PSA, CRM, finance, monitoring), since most strong companies have 10-15+ systems
  • A sponsor who will consider an exclusive license for an agreed term

The tech stack audit template shows a simple way to note documentation tools, years of history and export paths without opening any content.

IT Glue versus other documentation platforms

The same logic applies if the MSP uses Hudu or another tool: what matters is not the brand but how long the history goes, how templates are separated from client content, and who can run an export. Do not assume a vendor limit or feature. Ask the MSP what it has kept and confirm with its own administrator.

What are the pitfalls?

PitfallWhy it hurtsFix
Treating the whole platform as the MSP'sClient environment data is mixed inScope to templates and generic procedures
Free-text secretsCreates a privacy and security riskThe MSP cleans these before any review
Asking the MSP to send samplesPartners must not handle recordsDescribe the process only
Assuming old revisions existSome teams overwrite rather than versionAsk the administrator

What does a documentation review look like for the MSP?

A review is a conversation about structure, not a read-through of articles. The MSP lists its documentation tools, the number of years each has been in use, the share of articles that are templates versus client-specific, and who can run an export.

QuestionGood signWeak sign
How long has the platform been in use?Many years, with revision historyRecently rebuilt from scratch
Are templates separate from client records?Yes, by designEverything mixed in one structure
Who can authorize an export?A named executiveNobody knows
Were older articles archived or deleted?Archived and retrievablePurged periodically
Do other systems capture outcomes?PSA, CRM and finance in placeDocumentation is the only record

If the MSP is weak on most rows, its documentation alone will not carry a review, and that is fine. Recommend it work on the basics, and revisit later.

What to say to an MSP owner

When is the timing right?

Raise it when the MSP is already thinking about its documentation: a platform renewal, a switch between documentation tools, a merger with another MSP, or a clean-up before a sale. Each of these forces someone to ask what exists, what it covers and how to get it out. A switch between tools is the most important, because an export taken before the old subscription lapses can preserve revision history that a fresh import may flatten.

How rewards work

Partners earn 25% of the eligible platform fees SourceX actually collects from the referred company's licensing deals, capped at $100,000 per referred company. Rewards become payable only after the buyer pays and SourceX receives its fee; none is guaranteed, and the reward is never deducted from what the MSP receives.

Next step

For MSP owners in your network, register as a partner and make an introduction. Related: referral opportunities for managed service providers, additional revenue streams for MSPs, vertical MSP specialization, the network opportunity finder and who qualifies.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Buyer selects and paysThe buyer selects and pays for the data and SourceX receives its fee.
  4. Step 4You get your rewardYour share of SourceX fees becomes payable.

Common questions

Are client passwords in IT Glue ever part of a licensing review?

No. Credentials, vault entries and environment details are never in scope. They belong to clients and carry security risk. Any review would be limited to the MSP's own material, with redaction rules agreed before any work begins.

Can an MSP license its runbooks?

Possibly. Runbooks the MSP wrote and owns, free of client confidential content, could be reviewed as part of a wider licensing opportunity. Rights review decides, and nothing is binding until the company agrees price and terms and signs.

Does the MSP need to use IT Glue specifically?

No. Any documentation platform with a meaningful history can matter. What counts is years of records, separation of templates from client content, and someone who can run an export.

What size must the MSP be?

The baseline is 50+ full-time employees at peak, with contractors excluded, plus several years of documented operations, rights to license and an authorized sponsor. Smaller MSPs do not qualify under the current baseline.

Should I ask the MSP to send me documentation examples?

No. Partners make introductions and give basic fit information only. Sending or describing confidential records is outside a partner's role and could breach client agreements.

Free resources

By SourceX Partnerships Team · Published 2026-10-09 · Updated 2026-10-09

Know a US company with valuable proprietary data?

Become a referral partner from anywhere we support, get your link and introduce an owner or authorized decision-maker.

Refer a company →

I own a business

Explore licensing your company's data to AI developers worldwide. Start a short assessment; no uploads needed.

Start an assessment