Recorded walkthroughs, inside the same permission model.
Loom records screen and voice walkthroughs and places them alongside the work in Atlassian, which is where handovers, demonstrations, and training explanations tend to be needed. Our work is adoption inside the estate, and the sharing and permission model that recordings require.
Loom captures the demonstrations and handovers that otherwise happen live and get lost. The governance question is who can see a recording, and it is the same question as every other one.
What it is
Loom records screen and voice walkthroughs and places them alongside the work in Atlassian, which is where handovers, demonstrations, and training explanations tend to be needed.
What it does
Walkthroughs where the work is
Recordings attached to the item they explain rather than in a separate library nobody opens.
Sharing that can be scoped
Default sharing settings are the thing worth deciding once rather than per recording.
Where it fits
L2, platform and migration. It sits with the collaboration tools rather than the governance ones. Its identity question is narrow but real: a recording is content, and sharing defaults decide who outside the organization can see it.
What we do with it
Adoption and enablement
Training and adoption programs, since a recording tool succeeds or fails entirely on whether people use it.
Sharing and access defaults
Deciding what leaves the organization by default, which is a five minute decision and an expensive omission.
Recording the handover
Administrator handovers and as-built walkthroughs captured while the people who built it are still on the engagement.
Where it earns its place
A team documenting a handover
Recorded walkthroughs are usually the only documentation an administrator handover actually gets.
An organization running training cohorts
Sessions recorded once and reused, rather than delivered live to each group.
Proof
Teamwork Solutions Finalist, 2026
Atlassian Partner Awards, 2026
Questions we get
Is there anything to configure?
Licensing
Loom is licensed per creator and is frequently bought by one team before an estate-wide entitlement is considered. That reconciliation sits with the rest of the estate in licensing and renewals.