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.
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.
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.
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
Professionals Get In Without A Row In Your Directory
The people an organization most wants to reach outside its own payroll tend to be professionals: applicants, partner staff, contractors, clinicians thinking about a move, alumni who still open work mail at six in the morning. Almost all of them keep a LinkedIn account current, and almost none of them want another password. On an external portal built on Nexus positioned as the Enterprise Video Platform, social sign-in puts LinkedIn on the sign-in page, and a visitor who picks it arrives as a known viewer with no account issued to them. LinkedIn stays their identity, and your directory does not gain a row for every person who watches.
How it connects
Social sign-in is licensed as its own feature and enabled per portal, separate from the corporate SSO app staff use. With it on, LinkedIn appears as a choice on that portal's sign-in page. The visitor authenticates at LinkedIn under LinkedIn's own policy and comes back signed in, so the portal never handles the password and creates no organizational account in advance.
Nexus acts as a service provider in that exchange and never as an identity provider. A LinkedIn identity sits outside your directory and brings no groups with it, so what a signed-in visitor may see and do is set in the portal rather than inherited from directory membership. For an external audience that is usually the point. Nobody has to decide which internal group a prospective employee belongs to, and the administrator sets the reach of that portal once instead.
The cost of that convenience is worth naming. You are not the party who can close these accounts, and nothing upstream will deprovision them for you, so the portal is where a visitor's access is reviewed and withdrawn. Enterprise portals usually go the other way and enforce sign-in to the organization's own provider, which is a different app under a different license.
What you can do together
Open an external portal without opening the directory
Applicants, partner staff and alumni reach Nexus with the LinkedIn account they keep up to date, and your directory stays an employee directory.
See who attended
A visitor who signs in is a named viewer, so a recruitment or partner session has an audience rather than a hit count.
Keep one portal external and another internal
Social sign-in is enabled per portal, so the public side can run on LinkedIn while staff portals stay on corporate SSO.
Offer the account each visitor actually holds
LinkedIn sits on the same page as the other consumer providers the administrator has enabled.
A scenario
- Setup, ITThe identity team enables LinkedIn social sign-in on the residency portal and sets what a signed-in visitor may open. The staff portal keeps its corporate SSO app, licensed separately and unchanged.
- MondayNurse recruitment publishes a session on what the first rotation actually looks like, as public content on the residency portal.
- Wednesday, 12:20A nurse in another state opens the portal on her break, picks Sign in with LinkedIn and approves the request there. She watches the session, and the hospital created no account for her.
- Same weekAnother applicant signs in with a Microsoft account from the same page. Both are known viewers under the settings chosen for the residency portal, since neither identity carries a hospital group.
- Through the residency yearClinical training for employed staff stays on the staff portal behind corporate SSO. LinkedIn sign-in reaches the residency portal and nothing beyond it.
What stays where
LinkedIn remains the visitor's identity
The account and the password belong to LinkedIn and to the person, and the portal stays a service provider throughout.
Your directory stays an employee directory
A LinkedIn identity is outside it and carries no groups, so entitlement for these visitors comes from the portal's own settings, and so does withdrawing it.
Nothing changes for staff
Corporate SSO is a separate app under a separate license, and enterprise portals go on enforcing sign-in to your own provider.
Deployment is your choice
Shared SaaS, a dedicated cloud, or servers you run yourself.
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.
Request a demonstration or write to sales@vidizmo.ai
sales@vidizmo.ai · vidizmo.ai/integrations/catalog/linkedin