JiveContent Management and Web
The Town Hall Plays Inside the Thread About It
No Jive add-on exists for this, and none is needed. The connection is an embed code and a JavaScript widget pasted into a page, the same path the shipped WordPress and SharePoint integrations run on, and it holds anywhere a page renders HTML. Jive is where the internal communities live, the announcements and discussions people open each morning, and video has usually sat somewhere else with its own address and its own list of who may watch. A community page carries the player itself, while Nexus, the portal behind the Enterprise Video Platform (EnterpriseTube) solution, keeps the recording, the access rules and the record of who watched.
What you can do together
- Keep the conversation and the video in one place, with a town hall recording playing inside the thread discussing it rather than linked elsewhere.
- Give a team its own library, with gallery, detail and search widgets on its community page and no second system to administer.
- Gather a response under the player, using the quiz and survey player widgets in the same page.
- Learn which community actually watches, since embed analytics report the sites that embedded an item, the view count for each and the last playback.
How it connects
A community manager works in Jive as now. Placing a widget means pasting it or an embed code into a page, the same action as adding any other embedded content. Nothing is installed in Jive.
Communities are not limited to a single player. The documented widgets include video, audio, image, document, collection and playlist players, media library gallery and detail views, insights, transcription, maps, carousel and collage, quiz and survey players and a mashup filter, so a team space can carry a browsable video library, a search box across it, or a survey under the recording.
Access stays with the library. Embedding is restricted to approved domains, so the intranet is named and any host outside it refused, and content URLs are signed and expire. Each embed resolves against the viewer's identity, so a recording limited to one group in Nexus stays limited on a community page every employee can open. Discussions, membership and moderation stay Jive's business.
What does not exist is the other direction. There is no ingestion connector for Jive, so content held in Jive is not pulled into the library. Ingestion is a per-source connector and the built ones are SharePoint, OneDrive, Kaltura, Azure Blob, AWS S3 and Teams. One thing worth naming: Jive is a long-established platform under Aurea, so an engagement should confirm the release in use before assuming a page will accept arbitrary markup.
JiveContent Management and Web
A scenario
- SetupAn administrator adds the intranet to the approved domain list in Nexus.
- Tuesday, 09:00The quarterly all-hands recording is uploaded to Nexus, opened to all employees, and filed under the firm's retention rule.
- Tuesday, 11:00The communications manager pastes the player widget into the company news page and a survey widget beneath it. Both render in place, because the intranet is on the approved list.
- Tuesday afternoonAn engineer watches the all-hands inside the community, answers the survey and joins the discussion below it, without leaving Jive.
- WednesdayA safety team embeds an incident briefing limited to its own members. A colleague from another unit sees the discussion and not the video.
What stays where
Jive keeps the community
Discussions, membership, moderation and the intranet structure stay there, and nothing is installed for a widget to render.
The media stays in the library
The recording, its access rules, retention and the record of who watched live in Nexus.
Ingestion from Jive does not exist
Surfacing content in a community ships; pulling Jive's own content into the library is a connector that has not been built.
The release in use is worth confirming
Jive is long-established and now under Aurea, so whether a page accepts arbitrary markup is checked rather than assumed.
Products and solutions
Next step
See it on your own Jive instance.
We will show the connection made, the data moving and the output, then size it for your deployment.
Contact VIDIZMO
sales@vidizmo.ai
+1 571-969-2180
vidizmo.ai