Platform - Galleries

Reusable video galleries for every destination

Organize videos and documents into one structured collection, then embed it across product pages, help centers, training systems, and hosted Pages - without rebuilding the library for each destination.

Reuse one maintained gallery
Keep videos and documents together
Add VideoGPT when needed

Book a Demo Start Free Trial

One video and document gallery reused across website, help center, and training portal layouts

What Galleries are

More than a playlist. More than a widget.

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. With VideoGPT, the gallery can also become easier to enter: viewers can see what the collection covers, ask across the content, and jump to the source moment that answers them.

Collection

Group the right knowledge together

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.

Reusable delivery

Use the same gallery in more than one place

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.

Behavior

Keep the experience consistent

Templates, branding, player options, search settings, attached-document visibility, downloads, VideoGPT, and optional welcome-message behavior all stay tied to the gallery so the collection remains coherent wherever it appears.

AI-guided gallery orientation

Help viewers understand the collection before they browse

A gallery can be valuable even when it is not huge. A few long webinars, a focused set of tutorials, or a support playlist with many procedures can still be hard for viewers to enter if they do not know what is inside or where to start.

When VideoGPT is enabled, the gallery can open with a welcome message that explains what the collection covers and suggests useful questions based on the actual videos and documents inside.

Welcome message

The gallery introduces itself

VideoGPT can explain what the gallery covers, what types of videos and documents are included, and which subjects viewers can explore first.

Give users a starting point

Instead of forcing viewers to scan every item, the gallery can suggest practical questions based on the content it already contains.

Exact-moment answers

Move from question to source

When a viewer asks, VideoGPT can answer across the gallery and send them to the exact video moment or supporting document that explains the answer.

Why this matters

Keep knowledge consistent wherever the work happens

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. Even when the right video exists, viewers may not know which collection to open, what the collection covers, or where the exact answer appears.

Consistency and reuse

Fewer duplicated libraries — The same collection can support many deployment surfaces, so teams do not need separate video libraries for every site, page, or internal system.
Easier updates — Update the gallery once and the refreshed structure, videos, and attached documents stay aligned across the places where the collection is deployed.

Workflow delivery

Better workflow delivery — People learn faster when the right gallery appears inside the page, article, portal, or system they already use instead of sending them somewhere else.
Video and docs stay together — Walkthroughs, PDFs, release notes, technical guides, and support documents stay attached to the same gallery instead of drifting apart in different tools.

Operational payoff — Organize it once. Keep it useful everywhere. Galleries help teams maintain one structured collection and reuse it across the places where customers, trainees, support users, and internal teams actually need it. Consistency. Reuse. Fewer rebuilds.

How Galleries work

How Galleries organize, deliver, and improve knowledge

The workflow is simple: structure the collection, choose the right view, deploy it where the work happens, help people understand what is inside, then improve the library over time.

Choose the assets and order

Build the collection around the real task, not just around upload date. Group by topic, role, workflow, module, product line, issue, or audience.

Apply the right template and settings

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.

Deploy it where the work happens

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.

Let users browse, search, ask, or start from a welcome message

Search and attached documents make the collection easier to use. VideoGPT can add a welcome message, suggest starter questions, answer across the gallery, link to the right source, and jump users to the exact moment that matters.

Measure and improve

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.

Structure / delivery / discovery

Structure

Galleries

The collection layer where videos, documents, templates, settings, and grouping logic come together into one reusable library.

Delivery

Embeds, hosted Pages, and direct single-video delivery

Use the same organized gallery in the destination that fits the audience instead of rebuilding the content for each surface.

Discovery

VideoGPT across the gallery

VideoGPT can work across galleries so users can understand what is inside, ask across the collection, get grounded answers, and jump to the right source or moment.

Deployment surfaces

Where teams embed Galleries

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.

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.

Documentation and support systems

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.

Training environments

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.

Internal portals and intranets

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.

Partner environments

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.

Hosted destinations when needed

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.

Galleries, Pages, and Tube

Three product shapes, three different jobs

Pages and Tube still matter. Galleries simply own the embed-first story.

Galleries

Reusable embedded collection layer

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.

Best when the knowledge needs to live inside existing workflows and stay reusable across more than one surface.

Pages

Hosted destination

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 Pages

Tube

Portal environment

Use Tube when the rollout needs a true portal with workspaces, channels, permissions, repeat-usage behavior, and a destination people return to over time.

Explore Tube

Reuse and consistency

Scale one working gallery into many consistent surfaces

The 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.

Master galleries

Keep multiple gallery instances aligned

Use a master gallery to keep branding, layout settings, player behavior, and customization consistent across linked gallery instances.

Template logic

Change the shape without rebuilding the library

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.

Video + document knowledge

Keep supporting materials with the collection

Pair walkthroughs with release notes, technical documentation, onboarding guides, and service PDFs so the gallery stays complete wherever it is deployed.

Light security

Protect the collection where needed

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.

What teams build with Galleries

A practical starting point for real knowledge rollouts

Galleries are often the cleanest first move because they work well when one team needs structured knowledge in one environment before anything broader exists.

Solution fit

Product Education

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. VideoGPT can help viewers understand what is inside and ask for the exact walkthrough they need.

Explore Product Education

Solution fit

Support & Troubleshooting

Deploy 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, with answers that can point to the exact visual step.

Explore Support & Troubleshooting

Solution fit

Embedded training

Use 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. Suggested questions can help learners find the right lesson without browsing every item.

Explore Video Training Portals

Solution fit

Internal Knowledge Base Software

Use 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 Base Software

Customer examples

How teams use Galleries across product education, support, and training

Galleries 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.

Large reusable gallery system

Leidos

Embedded product education

Product educationhosted training Pagesdemosrelease updatesrole-based learning paths

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.

What Leidos built: A structured gallery setup supports embedded delivery, video-and-document pairing, and reusable organization across multiple product education surfaces.

Deployment highlights: Hosted Pages, attached documents, role-based grouping, and VideoGPT all work inside the same gallery-based setup, helping viewers understand the collection and move to the right source faster.

Explore Leidos

Distributed embedded knowledge

Verily

Distributed embedded knowledge

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.

More than a thousand videos across multiple systems
More than a thousand PDFs paired with the knowledge layer
Strong fit for reusable embedded knowledge delivery

Support and training

Chamberlain

Support and training

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.

Around 400 videos across support and training environments
Structured playlist galleries across support docs, academy, and hosted pages
Strong fit for gallery reuse in technical product ecosystems

Explore Chamberlain

FAQ

Frequently asked questions

What is a gallery in Cincopa?

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.

How is this different from a playlist or a video widget?

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.

Where can we embed galleries?

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.

Can one gallery support more than one surface?

Yes. One gallery can support many deployment surfaces, including hosted Pages, while keeping the same structure, attached documents, template logic, and discovery layer intact.

Can we keep PDFs, guides, and release notes attached to the videos?

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.

Where do Pages and Tube fit?

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.

Where does VideoGPT fit?

VideoGPT can work across galleries. Users can see a welcome message, ask across the collection, get grounded answers, and jump to the exact moment or source that matters. Galleries still remain the reusable collection story, with VideoGPT as the discovery and answer layer.

Can a gallery introduce itself before users search?

Yes. When VideoGPT is enabled, a gallery can show a welcome message that explains what the collection covers and suggests useful starter questions based on the videos and documents inside.

What is a master gallery?

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.

Can galleries be protected?

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.

Is this a good place to start?

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.

Next step

Build one gallery that can work across more than one surface

Start with one product area, one documentation surface, one support library, one internal portal, or one embedded training flow. Get that collection working well, help viewers understand what is inside, then reuse the same gallery across adjacent destinations without duplicating the library.

Book a Demo Start Free Trial