EdgeVISS Cloud Manager
Multi-Tenant Management
One Manager instance serves every customer you run — each with their own projects, sites, devices, team, and licensing, cleanly scoped from each other.
The hierarchy
Each level is created from the one above — the UI enforces the order, not just the diagram.
1
Customer
The organization you manage devices, projects, and licenses for. Contact email, status, created date.
2
Project
Groups sites and devices under one customer — e.g. "Plant Automation." A project cannot be created until its customer exists.
3
Site
A physical or logical location within a project — e.g. "Main Plant," with an address. A site cannot be created until its project exists.
4
Device
One EdgeVISS Local gateway, enrolled and tracked from here — health, commands, deployments, and licensing all resolve back up through this same chain.
Why the structure holds up
Everything downstream resolves through this chain
Plans cap gateways per customer. Gateway licenses record a customer name and gateway ID. Deployments, audit entries, and the Engineering Workspace all trace back to a real customer/project/site — never a flat, unscoped device list.
Team access is organization-scoped
A signed-in member belongs to exactly one customer (profiles.customer_id) with a role of admin or member. An org admin invites teammates and controls who can remove whom — no cross-customer visibility by accident.
Platform-admin-only surfaces stay separate
Gateway Licenses, the Audit Log, and Registry Providers are gated to platform admins (role=admin with no customer_id) — a customer's own admin manages their team and devices, never another customer's licensing ledger or registry credentials.
Team access, per organization
An organization admin invites teammates by email — they land as Admin or Member, scoped only to that customer's own devices, projects, and sites. Admins can revoke a pending invite or remove a member (never themselves, so an org can never lock itself out).