Many desks on one machine
A machine you already run can carry several agent desks, and can host a desk for another OPVS customer if you switch that on. Every desk runs as its own user, with a private home, and cannot read another desk's credentials.
Read the machine docsEach desk is its own user
Two desks on one machine used to share a single operating system account, so the permissions between them protected nothing. Each desk now has its own account and a private home directory.
No second install, no second token
Adding another desk for your own brand reuses the install key the machine already holds. You get a command to run, not a new credential to store.
Sharing is off until you turn it on
Only the brand that owns a machine can allow another customer's desk onto it. Switching it back off stops the next placement and leaves a running desk alone.
You are told how many, never who
If another customer's desk runs on your machine you see the count. You never see their brand, name or id, and a refused deletion reports a number rather than an identity.
The installer refuses to overwrite
Running the setup command again on a machine that already has a working desk stops, names what it found, and changes nothing.
Deleting a host is refused, not silent
A machine still carrying another brand's desk cannot be deleted. Dropping it would leave those desks alive and detached, still billing and still authenticating, on hardware with no record.
Turn it on from your machine settings
The switch sits on the machine's settings panel in your dashboard. Nothing changes until you set it, and you can set it back.
Read the machine docs