VR3 AI is multi-tenant: every resource (agents, campaigns, telephony configurations, runs) belongs to an organization, and access is governed by per-organization roles and explicit sharing. There is no public sign-up — accounts are provisioned by an administrator.

​
Users and roles

Each user has a role within an organization:
RoleCapabilities
MemberCreate and manage their own agents; use any agent explicitly shared with them.
AdminEverything a member can do, plus full access to every resource in the organization and the ability to manage members.
SuperuserPlatform-wide administrator. Access to the Admin panel across all organizations; can create users, manage organizations and memberships, and permanently delete archived agents.
There is no self-service registration. An administrator creates each account; the user signs in with the provided credentials and is required to change their password on first login.

​
Organizations

A user can belong to more than one organization and switches between them with the organization switcher in the sidebar. The selected organization scopes everything you see — the agents list, campaigns, telephony configurations, and the usage/agent-runs view all reflect the current organization only.

​
The Admin panel

Superusers get an Admin entry in the account menu. From there you can:
  • Create users — provision a new account with an email and temporary password (the user changes it on first login).
  • Manage organizations — create organizations and rename them.
  • Manage memberships — add or remove users from organizations and set their role (admin or member).
  • Grant superuser — promote or demote platform administrators.
  • Permanently delete archived agents — a hard delete that removes the agent and all of its data (definitions, runs, recordings, and any shared-access grants).

​
Sharing agents

Members own the agents they create. To let a colleague use one, the owner (or an organization admin) shares it with a specific user at one of three permission levels:
PermissionGrants
View onlySee the agent and its configuration.
RunView, plus start calls and test the agent.
EditView and run, plus modify the workflow.
When a shared user runs an agent, the call executes under the owner’s configuration (their model/provider settings), while usage is attributed to the organization the run belongs to. Access is always evaluated server-side: a user who is neither the owner, an admin, nor an explicitly shared user cannot view, run, or edit the agent.