Why do multi-site video systems need roles and permissions?
One site with one operator can get by with a single login. Add a second property, a regional manager, a contractor and a security partner, and shared passwords become a liability. Nobody can say who steered a camera or exported a clip, and removing one person means changing a password for everyone. A multi-site platform solves this by giving every person an individual identity and attaching rules to that identity, so access follows the job instead of whoever happens to know the password.
There is also a privacy and safety angle. A camera that looks at a parking area is different from one aimed at an entrance used by employees. Limiting who can view, rewind or download each feed reduces the chance of misuse and makes policy easier to enforce. It is a basic expectation of procurement and legal teams reviewing a video system, and it is far easier to design in from the start than to bolt on later.
What is the difference between a role and a permission?
A permission is a single allowed action, such as view live video, view playback, control PTZ, export a clip, change settings or manage users. A role is a named bundle of permissions, such as viewer, operator, site manager or administrator. Assigning roles is faster and less error prone than ticking dozens of boxes per person, and changing the role definition updates everyone who holds it at once, which keeps large teams consistent over time.
The second dimension is scope. A role says what someone may do; scope says where. A regional manager may hold the manager role across ten sites, while a contractor holds a viewer role on one camera for the duration of a project. Good systems let you combine the two cleanly, and let you set expiry dates for temporary access. Ask any vendor to show how scope and role interact, because that is where mistakes in configuration usually hide.
What are sub-accounts and how do dealers use them?
A sub-account is a child environment created under a parent account. An integrator or dealer who installs systems for many customers uses a parent account to create one sub-account per customer. Each customer sees only their own sites, cameras, users and layouts, while the dealer can step into any of them to configure, troubleshoot or monitor. The customers are isolated from one another, which is essential when the dealer serves competitors or unrelated businesses.
Delegated administration also reduces friction. The dealer can create the customer's first administrator, who then adds their own staff without calling the dealer for every change. Billing, branding and default settings can often be managed at the parent level. The trade-off is responsibility: the dealer holds a powerful position, so the platform should record which parent-level users entered which customer account, and customers should know the terms of that access.
How do audit trails and least privilege protect you?
Least privilege means everyone gets the smallest set of permissions that lets them work. A night supervisor who only needs live view and PTZ should not be able to delete recordings. If that supervisor's credentials are stolen, the damage is limited to what the role allowed. This principle is the single most effective control available in access management and costs nothing but a little planning, and it is usually the first thing a careful auditor or insurer asks about.
An audit trail is the record that makes the principle checkable. It logs sign-ins, camera views, PTZ commands, exports, setting changes and user changes, with who and when. After an incident, it answers whether a clip was exported, by whom, and from where. Review it periodically, not only after problems. Confirm how long logs are kept and whether administrators can alter them, because a log that can be edited quietly is a weak safeguard.
How should you set up roles for a new deployment?
Begin by listing the real jobs: who watches live, who investigates, who administers, who only needs to see a report, and who supervises the people doing all of that. Draft three or four roles that match, resist creating a unique role for every person, and map each role to sites. Make exports and user management the most restricted permissions, since those carry the most risk. Pilot the setup with a few users before rolling it out widely.
Plan for change. People leave, contractors finish, and sites are added. Build an offboarding step that removes access the same day, and a quarterly check that lists who can reach what. Use individual accounts even for shared monitoring screens where possible, or restrict shared accounts to view-only. When working with a dealer or integrator, write down what level of access they hold, and confirm the terms with counsel where contracts or privacy law apply.
Key terms
- Role
- A named bundle of permissions, such as viewer, operator or administrator, assigned to a user to define what they can do.
- Permission
- A single allowed action in the platform, for example viewing playback, controlling PTZ, exporting a clip or managing users.
- Scope
- The sites or cameras a role applies to; the same role can cover many sites for one person and one camera for another.
- Sub-account
- A separate customer environment created under a parent dealer or integrator account, isolated from other customers.
- Least privilege
- The principle that each user receives only the access needed for their job, limiting the harm from mistakes or stolen credentials.
- Audit trail
- A time-stamped log of sign-ins, views, commands, exports and setting changes that shows who did what.
For a company running several trailers across different properties, the practical question is who can see which unit. AI VisionStream supports multi-site management with roles and permissions, and sub-accounts so dealers can set up separate customer environments. A property manager might see only their own trailers, a security partner might get live view, and only a few people might export evidence.
Common questions
What is a sub-account in a video platform?
A sub-account is a separate customer environment created beneath a parent account, usually by a dealer or integrator. The customer sees only their own sites, cameras and users, while the parent can enter to configure or support them.
Should every user have their own login?
Yes. Individual logins let you attribute actions, revoke one person without disrupting others and apply different permissions. Shared passwords hide who did what and make offboarding slow and risky, so they should be avoided wherever practical.
Who should be allowed to export video?
Keep export to a small group, because exported footage leaves the platform's controls. Typically that means managers or investigators. Others can view and flag moments for them. Confirm retention and sharing rules with counsel or the local authority where required.