LinkedInIdentity and Access · Productivity and Collaboration
Alumni Carry Your Public Lecture Into Their Own Network
An alumna who posts a lecture to her LinkedIn feed is recommending it to a few hundred people who know what she does for a living and why she bothered. That is a different thing from an institution posting about itself, and it is the reason a share control in the player matters on an external portal. On Nexus positioned as the Enterprise Video Platform, the control posts a link to public content on LinkedIn. The recording stays in the portal under the access rule it already had.
What you can do together
Let the attendee do the distribution
Someone watching a public session on Nexus posts the link to their own feed straight from the player.
Reach the right desk rather than the widest feed
A link on LinkedIn travels among colleagues, peers and former classmates in the same field, which is where research talks, recruitment sessions and partner briefings are worth something.
Keep internal training internal
Sharing works only on content already published publicly, so a course built for employees offers nothing to press.
Switch it on per portal
An external portal carries the control while the staff portal does not, because the setting belongs to each portal separately.
How it connects
Social sharing is a portal setting. An administrator turns it on and the share control appears in the player, delivered as a JavaScript widget, the connection method the catalog names for this record. Leave the setting off and the player shows no share control, which is how a staff portal stays out of this entirely.
The control works only on material already published publicly. Pressing it therefore cannot widen access to anything: whoever follows the link from LinkedIn sees exactly what any member of the public could see without it. Internal training has no shareable link because it was never public in the first place, so the decision that governs sharing is the one made at publication.
What travels to LinkedIn is a link. The video file never leaves the portal, so retention and access rules continue to apply to the one copy that exists, and nothing flows back from LinkedIn into the portal. What the administrator is choosing, then, is narrow: whether this portal's players carry the control at all. Who follows a link once it is on a public network is nobody's decision, which is why the setting is paired with the publishing choice rather than standing on its own.
LinkedInIdentity and Access · Productivity and Collaboration
A scenario
- SetupThe web team turns on social media sharing for the lecture portal, and the share control appears in the player. The internal course portal is left as it was.
- Tuesday, 18:00A guest lecture on grid economics is published as public content. The faculty meeting recorded that afternoon is not.
- Tuesday, 19:30An alumna watching from another city presses the share control and posts the link to LinkedIn with a line on why it is worth the hour. The recording stays on the university's portal.
- WednesdayEngineers in her network follow the link and watch the lecture at its source. They reach that lecture and nothing else the university holds.
- ThursdayA lecturer asks whether the faculty meeting can go out the same way. It cannot. The recording was never published publicly, so its player carries no share control.
What stays where
LinkedIn receives a link
The video file stays in Nexus, and no copy of the recording is made on LinkedIn. Nothing comes back the other way either.
Publication is the gate
Only material already published publicly can be shared, so a viewer pressing the control cannot widen access to anything restricted.
Each portal answers for itself
Sharing is enabled per portal, so an internal one runs without the control while an external one carries it, and turning it off changes no one's access.
None of this moves the deployment
The portal runs as shared SaaS, in a dedicated cloud, or on your own servers.
Products and solutions
Next step
See it on your own LinkedIn 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