VAS Companies
0
Organisation hierarchy
VDL Platform → VAS Company → Tenant → Tenant user
Platform users govern VAS Companies and Company administrators. Tenant business operations stay inside the owning Company; privileged support enters through governed impersonation.
Active
0
Awaiting activation
0
Suspended
0
VAS Companies
Select the company boundary before managing actors or tenants.
Safe operating flow
Every action stays inside an explicit boundary.
- 1
Select a VAS Company
Govern Company lifecycle and administrators only. - 2
Handoff Tenant provisioning
The Company administrator owns Tenant creation and operations. - 3
Impersonate one hop
MFA, reason and ticket are required at every hop.
VDL global control-plane identities
Platform users
Govern named VDL Platform operators separately from VAS Company and Tenant users. Role and permission changes revoke existing sessions and require an explicit change reason.
Four-eye control: carrier-ingress certification and activation are separated. Use
platform_carrier_ingress_activator for a least-privilege independent activator; normal invitations cannot assign the break-glass super-administrator role.VAS Companies
Manage first-class company boundaries. Each company owns its users, tenants and tenant actors.
| Company | Contact | Country | Status | Last updated | Action |
|---|
First-class company actors
VAS Company users
Invite users, assign company roles, govern access and begin the first authorised impersonation hop.
Boundary: Select a VAS Company. Company users are not tenant users and cannot be moved across companies.
Company-owned organisations
Tenants
Create, activate or suspend tenants, then enter a tenant as a separate governed support hop.
Company: Select a VAS Company
Tenant-owned actors
Tenant users
Provision initial ownership and perform permitted support administration. Tenant owners keep routine administration.
API-first usage guide
Organisation and support flow
This UI is a small operational guide over the same governed API contracts used by integrations.
Normal administration
- 1. VDL: onboard and activate a VAS Company.
- 2. Company admin: invite company users and create tenants.
- 3. Company user: provision the initial tenant owner.
- 4. Tenant owner: manage tenant users independently for routine work.
Privileged support
- 1. Select company user and supply MFA, reason and ticket.
- 2. Select tenant and re-authorise the tenant hop.
- 3. Select tenant user and independently re-authorise again.
- 4. Use the persistent banner to return one level or end the chain.
No transitive authorisation, upward impersonation, cross-company/tenant access, secret disclosure or ordinary sensitive mutation is permitted.
Governed support sessions
Review recent chains and force-end an active chain when security or support policy requires it.
No impersonation sessions are visible to this administrator.