Tool trainers: teaching the software while the conversation is happening
Tool trainers in Outdoo teach a specific application. The trainer shares its screen during the session, so it can point at the field it is describing.
Outdoo's Resources library centralizes playbooks and SOPs, attaching them to roleplay agents, scorecards, and courses.

The compliance team's SOP, the enablement team's playbook, and the sales manager's scorecard used to live in three different places, each one a slightly different version of the same standard. Now they can all point to the same file.
As a training program grows, the same reference material tends to get copied into multiple places: pasted into a roleplay agent's prompt, retyped into a scorecard, attached separately to a course. Each copy can drift from the original the moment someone edits one but not the others.
A rep practicing against an outdated objection-handling script while being scored against an updated one is not a hypothetical, it is what happens by default once a playbook update does not propagate everywhere it was used.
Resources is a centralized library for reference documents, playbooks, SOPs, compliance guidelines, product one-pagers, and objection scripts, accessed through Manage > Resources. Supported formats include PDF, Word, plain text, CSV, and Excel, along with YouTube links added directly without a file upload.
Once uploaded, a resource can be attached wherever it is needed: to a roleplay agent so the AI buyer's objections and context are grounded in the real document, to a scorecard so grading criteria reference the same material, or to a course so the training content stays consistent with what reps are practiced and scored against.
There is no cap on reuse, a single document can sit attached to multiple agents, scorecards, and courses at once. Because the document lives in one place, an update to the source resource is reflected everywhere it is attached, rather than requiring a manual edit in every location that previously had a copy. In a course specifically, an attached resource shows up in a Learning Resources tab that learners see directly alongside the practice activities, not just as an invisible input feeding the AI.
An enablement manager rolling out an updated pricing SOP can upload it once and know that the roleplay agents testing pricing objections, the scorecards grading pricing conversations, and the course explaining the new pricing tiers are all referencing the identical document.
A compliance team in a regulated industry like insurance or financial services gets a single source of truth for approved language, so a rep's practice sessions, their scored feedback, and their required training all trace back to the same governed material rather than three versions that quietly disagreed.
A support enablement lead can upload an updated de-escalation script once and have the roleplay agent simulating an angry customer, the scorecard grading whether the steps were followed in order, and the certification course new hires complete before taking live calls all point back to that same file.
Full details are in Managing resources.
Launched in v3.3 (March 2026), the failure mode this closes was never a lack of documentation, most teams have plenty of it. It was that the same standard existed in three copies the moment it got used in three places, and nobody was responsible for keeping them in sync.
Consistency across a training program was never a matter of writing better documents, it was a matter of having only one copy of them.
Tool trainers in Outdoo teach a specific application. The trainer shares its screen during the session, so it can point at the field it is describing.
Skill trainers in Outdoo teach applied practice. The trainer takes a part in the conversation, pushes back, and tells your team what to do differently.
Concept trainers in Outdoo teach foundational knowledge from your own documents. Attach a plan summary and your team learns it by talking it through.
A 30-minute walkthrough built around your team's calls. When you're ready, prove it with a proof of concept.