Corporate training

Training video that stays inside the organisation

Internal video should not be on a public platform, and it should not be a 900 MB file circulating on a shared drive either. Host it once, embed it in the intranet or LMS your staff already use, and let the systems that own identity keep owning it.

Start free trialTalk to us

Recorded once, watched inside the organisation

The problem

How internal training video usually goes wrong

Two failure modes, and most organisations have both running at once.

Without control

Files on a drive, or a link on a public platform

Either version leaks control: nobody knows which copy is current, or the content is sitting on somebody else’s platform.

  • Multiple versions of the same module, and no way to tell which is current.
  • Large files that people download, keep and forward.
  • Unlisted public links that remain valid after a training assignment ends.
  • No usable signal about whether anyone actually watched.

On your own terms

Hosted once, embedded where staff already are

One canonical copy, delivered into a page your organisation controls and already authenticates.

  • Update the video and every embed of it is current.
  • Adaptive playback, so a home connection is not a barrier.
  • Playback restricted to your own domains rather than open links.
  • Aggregate engagement, so you can see which modules lose people.

The workflow

How this fits with what you already run

The critical step is assigning clear ownership for employee identity, playback access and the formal completion record.

  1. 01

    Separate content with projects

    Use projects to separate training from external communications, and to separate populations that need different protection or different embed rules. Settings live on the project, so this is also how protection is applied.

  2. 02

    Embed in the intranet or LMS surface

    A standard web embed goes on the page staff already use. Whether a specific destination accepts it depends on that platform’s HTML, script and content-security rules — test the embed in your own environment before planning a rollout.

  3. 03

    Let your own systems own authentication and access

    Let the intranet, SSO or LMS responsible for employee identity authenticate the page. Configure DynTube domain restrictions and signed, expiring links for the playback handoff, and confirm any additional identity requirement with us in writing.

  4. 04

    Keep the completion record where the obligation lives

    On Plus and larger plans, pass your own employee ID or email address with the embed to add per-user viewing reports. Keep the formal completion rule and audit record in the LMS or HR system that owns the training obligation.

  5. 05

    Review training engagement and revise the content

    Completion rate per module tells you which training is losing people and roughly where. That is an instructional-design signal, and it is what this reporting is genuinely good for.

The mechanisms

What the platform contributes

Delivery, protection and reporting mechanisms, with the relevant project and plan scope attached.

Adaptive HLS deliveryEvery viewer
Uploads are transcoded into a quality ladder and the player selects a rung from the connection it observes — which matters when staff watch from home or on mobile data.
Origin-restricted playbackPer project
Playback keys follow the allowed-domain list you configure, so with a non-empty list and the account-level key exemption off a module embed does not keep working if the page is copied outside your estate.
Signed, expiring linksPer request
Where a link has to go to a contractor or an external partner, it can be signed, time-limited and view-limited rather than permanent.
On-demand protection modesEntitlement-dependent
A project uses AES-128 or certified DRM, not both. DRM is entitlement-gated — confirm availability for your plan before designing a rollout around it.
Viewer watermarkingWhen data is available
The overlay uses server-supplied viewer data for attribution when identity exists. An authorised viewer can still record their own screen, so combine watermarking with origin restrictions and expiring access instead of treating it as a prevention guarantee.
Aggregate reportingPopulation level
Plays, watch seconds, completion rate and aggregate audience views per module.

Fit

When this is the right shape

These are the workflows where hosted training video and organisation-owned learning records fit together cleanly.

  • Best for — delivery for an existing LMS

    You already have a learning platform that handles enrolment and records. You want the video to be fast, current and not on a public platform.

  • Best for — intranet and distributed teams

    Onboarding, policy and equipment training embedded in the pages staff already visit, playing acceptably on home and mobile connections.

  • Best for — confidential internal material

    Origin restrictions, expiring links and watermarking where a leak would matter and attribution is worth having.

  • Connect viewing to the training record

    Keep enrolment, quizzes, certificates and formal completion evidence in the organisation-owned LMS. Use aggregate reporting and eligible per-user viewing reports as inputs to that record, and confirm the handoff with us in writing.

Test the embed in your own intranet first

Upload one module, embed it on a real internal page, and check it on a home connection. That answers the compatibility question that decides everything else.

Start free trialTalk to us