A workspace installs one Data Visions program on its PCs, the Bridge Harness, and everything else rides inside it as a connector: the camera recorder, the endpoint manager, the work order tray app, shared folders and more. Your module names the connectors it needs, and the Workspace Admin turns them on, computer by computer. No installers to email around, no separate sign-ins.
Two kinds of connector
Every connector runs one of two ways. Data Visions sets which, and your module can't change it.
| Service (shown as PC) | Session (shown as People) | |
|---|---|---|
| Runs for | The whole computer, even when nobody is logged in | Each person signed in to the Bridge Harness, as that person |
| Good for | A camera recorder, PC monitoring and patching | A person's own tools: work orders, notifications, shared folders |
| Who turns it on | A Workspace Admin, per computer | Issued to people as Assigned (installs by itself) or Allowed (they click Install) |
A connector never has a login of its own. The Bridge Harness holds the sign-in, and the connector's window just says which workspace and account it's connected through.
Shared folders
The Shared folders connector lets a person share folders from their own PC with their workspace's agents. It's a session connector that every workspace offers, so people install it themselves from the Bridge Harness window.
- View only or Can edit. When someone adds a folder, Windows asks whether agents may change files there. Can edit lets an agent save new files, or replace one only when it says so. Nothing is ever deleted.
- Once or Always. If someone tells an agent "upload the videos in my Trainings folder" and it isn't shared yet, their PC shows a notification: Once (view only, for the next hour), Always (a normal view-only share) or Not now. No answer in two minutes means no.
- Ask me first. A folder can ask before every read or save.
- Paths stay on the PC. The platform only knows the folder by its short label, and an agent can't step outside the shared folder.
Every read and save shows on the person's tray and goes in the workspace's activity log. Files can come in up to 200 MB, straight into your module's storage.
Want your module's own agent to use shared folders? Grant it the platform's shared-folder tools (see the developer snippet below). The Module Builder already has them, which is handy for testing with real files.
Turning a connector on for a computer
Your module declares the connectors it uses. That makes them available on the Bridges page; it doesn't install anything by itself.
- Open System settings, then Bridges.
- Click the computer's tile. The connectors on it show with their version and health.
- Click Install on the connector you need (or Update or Remove).
- Change its settings there if it has any, such as how many days of recordings to keep. The computer picks them up and confirms.
Session connectors are issued to people instead. A person then sees Issued to you in their Bridge Harness window, with Install for an Allowed one.
Ask the Module Builder
// For developers: module.json
"desktop_clients": ["VIDEO_CONNECTOR"],
"ai": {
"agent": {
"platform_tools": ["shared_folders_status", "shared_folder_request",
"shared_folder_list", "shared_file_import"]
}
}Good to know
- Connectors come from Data Visions. Your module picks from the ones the platform publishes; a module never carries an installer. Need a new one? Ask Data Visions.
- Your module talks to a connector through the Bridge, with the same calls as any Bridge tool. See The Bridge.
- One person, several workspaces? Each workspace's session connectors run side by side, labelled, and never see each other's shares.
- Only Workspace Admins install connectors on a computer or change their settings.