Templates inside the channel
The same governed gallery as Word and PowerPoint, available where the conversation is happening — no switching apps, no downloading files.
← SolutionsSurface · Teams
Governed templates where the work actually happens.
Teams is where projects live — and where documents get created fastest and governed least. Kameleon brings the same governed templates, brand and metadata rules into Teams channels, so collaboration doesn't quietly create a second, ungoverned document estate.
WHAT IT COSTS TODAY
The daily tax nobody put on the roadmap.
- Documents get created in channels with no template, no metadata and no owner.
- Each project team invents its own folder and naming logic.
- Channel files drift out of the governed estate the moment they're uploaded.
- Nobody can tell which channel document is the approved version.
- Governance stops at the Office apps and never reaches collaboration.
In-channel
template access, no app switching
1 source
same governed templates as Office
Auto
naming, storage and metadata
0
shadow document estates
What changes on Monday morning.
Channel documents stay governed
Naming, storage location and metadata rules follow documents created in Teams, so channel work stays inside the managed estate.
One estate, not two
Project collaboration stops producing a parallel, ungoverned set of files that nobody audits and Copilot can't safely read.
“Every project channel had its own way of creating documents. That's not collaboration, that's fragmentation.”
FOR THE CIO AND DIGITAL WORKPLACE LEAD
The internal case, already written.
Collaboration platforms are where ungoverned content accumulates quietly. Extending governance into Teams is what stops the managed estate and the real estate from diverging.
- Extend document governance into collaboration, not just authoring.
- Keep project documents findable and classifiable by default.
- Remove the shadow estate before rolling out Copilot.
- Give project teams one obvious way to start a document.