Why one workspace should connect one seller account
How this boundary simplifies browser sessions, devices, permissions, billing, audit logs, and failover.
Browser sessions stay unambiguous
One Chrome profile normally has one active marketplace identity. Mapping a workspace to that seller prevents the extension from guessing which account owns a request, conversation, order, or action.
Customers with multiple seller accounts can create separate workspaces and keep their data isolated.
Devices become easier to reason about
Every registered device knows which seller workspace it serves. Active and standby election checks that workspace only. A device cannot accidentally execute a command for another seller connection.
Subscription limits and audits also become clear at the workspace boundary.
Teams can still collaborate
Many user accounts may join one workspace with different roles. They can manage orders and conversations from web or mobile while the active Windows device performs the browser action.
This provides collaboration without sharing the marketplace password among the team.