Web and product surfaces
Embed galleries in websites, product pages, product UI help layers, customer-facing resource areas, and knowledge bases where users need guided video and document knowledge inside the workflow.
Organize videos and documents into reusable collections you can embed across websites, product pages, help centers, documentation systems, LMS environments, internal portals, partner portals, knowledge bases, SharePoint, Salesforce, and hosted Pages.
A gallery is more than a playlist or a video widget. It keeps the structure, the template, the attached documents, and the viewing experience together so one maintained library can support many deployment surfaces.
A gallery is the reusable collection layer behind embedded video and document knowledge.
Each gallery defines which assets are included, how they are grouped and ordered, which template shapes the experience, what features are enabled, how attached documents appear, and how the collection behaves across every surface where it is deployed.
Organize videos, PDFs, and supporting assets by topic, role, workflow, product area, release, support issue, or audience so the knowledge matches how people actually look for answers.
One gallery can support product pages, documentation systems, help centers, LMS environments, internal portals, partner portals, knowledge bases, SharePoint, Salesforce, and hosted Pages without turning into separate disconnected libraries.
Templates, branding, player options, search settings, attached-document visibility, downloads, and VideoGPT all stay tied to the gallery so the collection remains coherent wherever it appears.
Most teams do not struggle because the video is missing. They struggle because the knowledge gets copied, split, stripped of context, and rebuilt across too many destinations.
The same collection can support many deployment surfaces, so teams do not need separate video libraries for every site, page, or internal system.
Update the gallery once and the refreshed structure, videos, and attached documents stay aligned across the places where the collection is deployed.
People learn faster when the right gallery appears inside the page, article, portal, or system they already use instead of sending them somewhere else.
Walkthroughs, PDFs, release notes, technical guides, and support documents stay attached to the same gallery instead of drifting apart in different tools.
Galleries help teams maintain one structured collection and reuse it across the places where customers, trainees, support users, and internal teams actually need it.
The workflow is simple: structure the collection, choose the right view, deploy it where the work happens, help people find answers, then improve the library over time.
Build the collection around the real task, not just around upload date. Group by topic, role, workflow, module, product line, issue, or audience.
Use the template that fits the environment, then configure navigation, metadata, search, downloads, branding, attached-document visibility, and player behavior around that audience and task.
Embed the gallery inside websites, product pages, help centers, documentation systems, LMS environments, internal portals, SharePoint, Salesforce, partner portals, knowledge bases, and other controlled internal systems where embeds make sense. The same gallery can also be published through Pages.
Search and attached documents make the collection easier to use. VideoGPT can then answer across the gallery, link to the right source, and jump users to the exact moment that matters.
See what people watch, what they search for, where questions repeat, and which topics need better coverage. Use that signal to tighten the gallery, improve supporting documents, and keep the collection more useful over time.
The collection layer where videos, documents, templates, settings, and grouping logic come together into one reusable library.
Use the same organized gallery in the destination that fits the audience instead of rebuilding the content for each surface.
VideoGPT can work across galleries so users can ask across the collection, get grounded answers, and jump to the right source or moment.
Galleries are built for reusable embedded deployment. One gallery can appear across many surfaces while keeping the same structure, attached documents, and viewing logic intact.
Embed galleries in websites, product pages, product UI help layers, customer-facing resource areas, and knowledge bases where users need guided video and document knowledge inside the workflow.
Use galleries inside help centers, documentation systems, support portals, technical articles, and troubleshooting pages so the right playlist and supporting docs stay close to the problem.
Add galleries to LMS environments, training pages, onboarding flows, academy content, and other learning systems when the library needs stronger video delivery and easier discovery.
Deploy galleries inside internal portals, intranet pages, team sites, SharePoint, Salesforce, and other controlled internal systems where embeds make sense and the content needs to stay current without duplicate libraries.
Use the same gallery inside partner portals, distributor resources, contractor training environments, and other external systems where structured video and document knowledge needs to stay consistent.
When a rollout needs its own destination, the same gallery can also support a hosted Page without losing the collection structure, attached documents, or discovery layer.
Pages and Tube still matter. Galleries simply own the embed-first story.
Use Galleries when the goal is to organize video and document knowledge once and deploy it across websites, docs, support systems, LMS environments, internal tools, and hosted Pages.
Use Pages when one audience, one program, or one rollout needs a branded hosted destination with its own access model, page-level shell, and viewer context.
Explore PagesUse Tube when the rollout needs a true portal with workspaces, channels, permissions, repeat-usage behavior, and a destination people return to over time.
Explore TubeThe most practical gallery advantage is not only the first deployment. It is the ability to keep a working collection consistent across many surfaces over time.
Use a master gallery to keep branding, layout settings, player behavior, and customization consistent across linked gallery instances.
Training-style playlists, category views, billboard-style player experiences, and simpler single-video layouts can all be driven by gallery and template choices instead of rebuilding the knowledge from scratch.
Pair walkthroughs with release notes, technical documentation, onboarding guides, and service PDFs so the gallery stays complete wherever it is deployed.
Galleries support password protection and domain locking for embedded environments. When a rollout needs deeper access control, Pages or Tube can add a stronger access layer on top.
Galleries are often the cleanest first move because they work well when one team needs structured knowledge in one environment before anything broader exists.
Organize onboarding, feature walkthroughs, role-based learning, and release education into reusable galleries that can be embedded across product pages, help centers, and supporting Pages.
Explore Product EducationDeploy structured troubleshooting libraries directly inside support docs, technical workflows, partner portals, and internal systems so users can find or ask for the right fix faster.
Explore Support & TroubleshootingUse playlist-style galleries inside an LMS, onboarding program, academy page, or internal training surface when the system exists but the video and document experience needs to be stronger.
Explore Video Training PortalsUse galleries as the reusable collection layer inside controlled internal environments so teams can organize training videos, recorded sessions, release updates, and supporting documents across Pages, internal portals, and other embedded systems.
Explore Internal Knowledge HubsGalleries support different knowledge jobs without forcing every deployment into the same front end. These examples show how teams use reusable galleries in embedded product education, distributed knowledge delivery, and structured technical support and training.
At Leidos, Galleries organize a large product education library with around 600 videos, about 150 galleries, and 350+ attached documents across embedded product pages, hosted training Pages, demos, release updates, and role-based learning paths.
A structured gallery setup supports embedded delivery, video-and-document pairing, and reusable organization across multiple product education surfaces.
Hosted Pages, attached documents, role-based grouping, and VideoGPT all work inside the same gallery-based setup.
At Verily, Cincopa is used as a distributed video-and-document knowledge layer across product UI, support documentation, LMS environments, internal systems, and development workflows.
At Chamberlain, Galleries support structured technical playlists across support documentation and training environments, especially where installers and technicians need to see the right step fast.
A gallery is a structured collection of videos and documents. It defines the assets, the grouping, the order, the template, and the behavior that shape how the knowledge is delivered.
A playlist or widget usually focuses on playback. A gallery also controls grouping, layout, metadata display, attached documents, settings, reuse across deployment surfaces, and how VideoGPT works across the collection.
Galleries can be embedded in websites, product pages, help centers, documentation systems, LMS environments, internal portals, SharePoint, Salesforce, partner portals, knowledge bases, and other controlled internal systems where embeds make sense.
Yes. One gallery can support many deployment surfaces, including hosted Pages, while keeping the same structure, attached documents, template logic, and discovery layer intact.
Yes. Galleries can pair video with attached documents so the user gets the walkthrough and the supporting reference material in the same reusable knowledge surface.
Galleries are the reusable embedded collection layer. Pages are the hosted destination layer. Tube is the portal environment for workspaces, channels, permissions, and repeat-usage behavior.
VideoGPT can work across galleries. Users can ask across the collection, get grounded answers, and jump to the exact moment or source that matters without the page becoming an AI-first story.
A master gallery is a shared setup that keeps linked gallery instances consistent. It is useful when many destinations need the same layout, branding, or player behavior.
Yes. Galleries support password protection and domain locking. If a rollout needs deeper access control, hosted Pages or Tube can add a stronger access layer on top.
Often, yes. Galleries are a strong place to start when one team needs structured, reusable knowledge in one environment before a larger portal or broader program exists.
Start with one product area, one documentation surface, one support library, one internal portal, or one embedded training flow. Get that collection working well, then reuse the same gallery across adjacent destinations without duplicating the library.