What Challenges do Enterprises Face Scaling Video in ServiceNow?
Share on Social
The ServiceNow Video Problem Enterprises Run Into First
Four pressure points show up almost immediately when video volume grows inside ServiceNow: access control, performance, governance, and user adoption. Who can see a recorded incident walkthrough? Will a 700 MB onboarding clip play cleanly for 40,000 employees on the same morning? Who owns retention and audit trails? And will anyone actually watch the content once it’s buried in a knowledge article?
Video behaves differently from text and images on the platform. A ServiceNow community discussion on video attachments notes that the default maximum attachment size is 1,024 MB and warns that large video files consume instance storage quickly, with instances commonly capped around 4 TB before more is purchased. Attachments also inherit record-level permissions rather than viewer-level video policy, and they stream from the instance rather than a content delivery network built for concurrent playback.
That turns the decision into a plain architectural question: attach video to records directly, embed a player from elsewhere, or route business video integration through a governed video layer that handles storage, delivery, permissions and analytics outside the instance.
The sections ahead map those options against real workflows — knowledge articles, case deflection, employee support — with current platform limits, an evaluation checklist and answers to the questions IT teams ask most.
Current-Year Data Shows Why Raw Video Attachments Break Down
Start with the numbers platform owners can check themselves. The same ServiceNow Community thread on video attachments cited above flags a practical risk beyond the size caps: depending on file sizes, a video library can hit the instance cap “rather quickly,” and admins have to maintain allow/deny lists for the file extensions users might upload.
Buying more storage moves the ceiling without fixing delivery. The same discussion notes that ServiceNow scales images, but the responder was not certain that behavior extends to video formats — which is precisely the question a knowledge article with 20,000 monthly views raises. A 900 MB training recording attached to a knowledge base entry has no transcoding profile, no adaptive bitrate ladder, and no edge caching, so a branch office on a constrained link pulls the same file as headquarters.
Delivery discipline is where platform teams already operate. A 2026 ServiceNow Community architecture post on an AI-driven delivery lifecycle argues for pipeline-controlled deployments, Automated Test Framework gates at every stage, and named governance control points — calling update set sprawl and absent CI/CD the compounding failures as platforms grow. Video hosted as loose binary attachments sits entirely outside that control model: no versioning, no audit trail, no rollback.
Translate that into evaluation criteria. File size is one constraint among several. Can an agent find the right clip through search? Does anyone see completion rates on a deflection video? Do permissions follow the viewer? The architectural split worth pressure-testing with any vendor is whether video is embedded as externally hosted, governed assets rather than stored media in the instance.
How Video Fits Into ServiceNow Knowledge, Support, and Case Deflection
Most ServiceNow video projects start in one of three places: a knowledge article, an employee support flow, or a self-service portal page meant to stop a ticket before it’s filed. Each one behaves differently, and each one breaks differently when video is handled as a file instead of a managed asset.
| ServiceNow surface | What video does there | What it takes to hold up at scale |
|---|---|---|
| Knowledge articles | A 90-second walkthrough of a procedure or policy replaces a wall of screenshots | Player embeds that respect article permissions, plus transcripts so the content stays searchable |
| Employee support flows (IT, HR, facilities) | Short recorded answers cut the back-and-forth on setup, benefits enrollment, and access requests | Adaptive playback for remote and branch users, and version control so an outdated clip retires cleanly |
| Portal and case deflection | A well-placed clip answers the top-volume question before a ticket opens | Viewership and drop-off analytics tied to ticket categories, so you know which videos actually deflect |
The delivery model is the part IT leaders should scrutinize. As noted above, ServiceNow’s attachment ceiling only stretches so far before it becomes a liability. Storing media there is legal but not sensible: raw files consume instance capacity, don’t adapt bitrate, and give you no view-level data.
Controlled business video integration keeps the media on a video platform with its own enterprise content delivery network options, while ServiceNow keeps the workflow, the permissions context, and the record. The buyer outcomes are the ones already on the roadmap — fewer duplicate tickets, stronger self-service, and one governance model instead of a scattered library.
What Enterprise Video Delivery Architecture Needs to do in ServiceNow
A ServiceNow instance is a workflow system of record, not a media origin. Given that same storage constraint described above, a handful of recorded all-hands sessions or training modules stored as attachments will crowd out the records the platform actually exists to run.
The roles are clear. The video platform handles video storage, processing, and delivery at scale, while ServiceNow simply references the video and displays the player. This lets video playback scale through the enterprise content delivery network rather than adding strain to the ServiceNow instance.
Four requirements decide whether that architecture holds up in practice:
- Permissions that mirror the workflow. If a knowledge article is gated by user criteria or role, the video inside it must respect the same entitlement — enforced through single sign-on and group mapping, with playback links that can’t be copied out and shared freely.
- Embed behavior that feels native. The player should load inline in knowledge articles, catalog items, and Employee Center pages, stay responsive on mobile, and carry captions — no pop-outs, no separate login prompt.
- Metadata and transcripts that feed search. Speech-to-text indexing and consistent tagging let a video surface in a ServiceNow search result alongside articles, instead of sitting in a library employees have to browse.
- Analytics platform teams can act on. View counts, completion rates, and drop-off points show which content deflects tickets and which segment loses viewers.
Where Vbrick Fits in a Governed ServiceNow Video Stack
The core architectural decision is whether video lives inside your ServiceNow instance or in a dedicated layer that ServiceNow points to. Uploading recordings as attachments works until it doesn’t — given that attachment ceiling and the storage pressure it creates, as noted above.
Vbrick takes the second path. Video is stored, transcoded, indexed, and permissioned within the enterprise video platform, then surfaced in ServiceNow through a native integration. Instead of moving video files into ServiceNow, Vbrick embeds secure player references directly into knowledge articles, catalog items, and agent workspaces. An enterprise content delivery network then handles last-mile video distribution at scale, offloading a function that records platforms were never designed to support.
That same governed layer is what lets Vbrick power ServiceNow Now Assist with video content. Because video is indexed and permissioned at the platform level, Now Assist’s AI Search can surface video results directly, and Genius Results can cite the source clip next to the article, not just the text. Virtual Agent answers draw on the same video-backed knowledge base, and developers can bring that content into custom skills and agentic workflows instead of limiting Now Assist to what’s written down.
The tradeoff worth weighing: a dedicated video layer is an additional platform to set up, integrate, and license. For a handful of short clips in one knowledge base, native attachments can be the simpler starting point. As video grows into a governed channel across thousands of employees, a dedicated platform gives IT the controls that scale — permissions, delivery, and analytics — that attachments alone don’t offer.
Practical Checklist for IT and Platform Teams
Before video goes live inside ServiceNow, work through five checks with the platform owner, the security team, and whoever runs your knowledge base.
1. Permissions. Map who can view, share, and edit each asset by role, group, and workflow state. Video permissions should mirror the article or case they sit on — an internal HR walkthrough embedded in a knowledge article shouldn’t be reachable by an unauthenticated portal user. Confirm the entitlement decision happens at the video platform, not just at the ServiceNow record.
2. Embed behavior. Test playback in knowledge articles, case pages, and the Employee Center portal, on desktop, mobile, and the browsers your workforce actually uses. Check that the player renders inside the record without breaking layout, and that a fulfiller can start a video mid-triage without leaving the ticket.
3. Searchability. Titles, descriptions, tags, and machine-generated transcripts should be indexed so a search inside the ServiceNow experience surfaces the right clip — not just the article that happens to contain it. Transcripts are what turn a video into something a search engine or an AI agent can read.
4. Analytics. Decide what you’ll measure before rollout: views, completion rate, drop-off points, and which questions still generate tickets after a video exists.
5. Storage and delivery. Given that same attachment ceiling noted above, instance storage is finite and fills quickly with large media files. Stream from a hosted platform with content delivery network and enterprise content delivery network support instead of attaching raw files — that’s the difference between a working business video integration and a storage problem.
FAQ: What Buyers Ask Before They Put Video in ServiceNow
What actually breaks when enterprises scale video in ServiceNow?
Four things, in roughly this order: access control, playback performance, governance, and adoption. The platform was built to manage work, not to serve media at scale, so the strain shows up as storage pressure, inconsistent permissions between the instance and the video source, and knowledge articles nobody can search by what was said on screen.
Should video be attached to records, or embedded from a video platform?
Attachments are fine for a one-off screen recording tied to a single case. They become a liability as a library — given that same attachment ceiling described above, every duplicate upload is charged against it.
Why does content delivery network-backed playback simplify things?
Because the file lives once, streams adaptively to the viewer’s bandwidth, and never inflates the instance. Embedded playback also keeps a single source of truth: update the master asset and every knowledge article referencing it reflects the change.
Who owns the video, and how is access controlled?
Ownership should sit with the video platform, with permissions mapped to the same identity groups governing the article. Ask any vendor to demonstrate revocation, version history and view-level analytics in a live instance.
For teams supporting knowledge, employee support and case deflection, treat business video integration as an architecture decision — see how Vbrick approaches secure video inside ServiceNow.