X (Twitter)Identity and Access · Productivity and Collaboration
A Public Notice Moves While It Still Matters
A public notice does most of its work in the first hour, and the people best placed to move it that fast are the ones already watching it. X is where that happens, in a timeline that reposts a boil notice or a closure before any newsletter goes out. On a portal built on Nexus positioned as the Enterprise Video Platform, a share control in the player posts a link to public content on X. The recording stays in the portal, under the access rule it already carried.
What you can do together
Post while the briefing is still current
A viewer of a public notice on Nexus sends the link to X in one action, from the player they are already in.
Travel through accounts people already follow
An outage notice or a safety message moves through residents, local reporters and neighborhood accounts rather than only your own channel.
Keep one authoritative copy
Everyone who follows the link arrives at the recording in the portal, so a correction or an update is seen by whoever gets there next.
Restrict it to the portal that should have it
Sharing is enabled per portal, so a public portal carries the control and an internal one does not.
How it connects
Social sharing is a portal setting. Switch it on and the player gains a share control, delivered as a JavaScript widget, which is the connection method the catalog names for this record. Where the setting is off, the player carries no share control, so nothing on that portal can leave this way. The decision is made once per portal rather than per recording, which suits an organization that keeps its public notices and its internal material on separate portals in the first place.
The control acts only on content already published publicly. Pressing it cannot widen access: whoever follows the link from X sees what any member of the public could already see on the portal. A recording that was never published publicly offers no share control at all, which means the publishing decision is the one that governs reach, not the player.
What travels is a link. The video file never leaves the portal, so there is one copy, held under its own retention and access rules, and the link resolves back to it. That matters most when a notice is superseded: people arriving an hour later reach the item itself rather than a stale duplicate sitting on a social platform.
X (Twitter)Identity and Access · Productivity and Collaboration
A scenario
- SetupThe communications team asks IT to turn on social media sharing for the public portal, and the share control appears in the player there.
- Tuesday, 06:15A main breaks in the north district. The utility records a two-minute briefing on the boil notice and publishes it as public content.
- 06:40A resident watching presses the share control and posts the link to X. The recording stays on the utility's portal, and what reaches X is the link.
- Through the morningNeighbors and a local reporter follow it and watch the briefing at its source, which is the copy the utility controls and can update.
- Later that weekThe post-incident review is recorded for staff and never published publicly, so its player shows no share control and it cannot go out this way.
What stays where
X receives a link
The video file stays in Nexus, and no copy of the briefing is made on X.
What was published is what can travel
Only content already published publicly can be shared, so pressing the control widens access to nothing.
The setting belongs to the portal
Sharing is enabled one portal at a time, and turning it off removes the control rather than changing what anyone may watch.
One copy, wherever the portal runs
Shared SaaS, a dedicated cloud or your own datacenter.
Products and solutions
Next step
See it on your own X (Twitter) 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