Velocity users must be assigned to roles before they can perform any tasks. Roles provide access to database sources and give users the privileges that they need to perform tasks. For example, users must have access to a database before they can use it to create a sandbox.
When a user has a user account in the Veritas Application Portal but has not yet been assigned a role, the user is considered unprivileged. An unprivileged user can sign in to Velocity, but cannot create or view anything in the system.
User accounts can only be deleted from Veritas Application Portal. When a user is deleted, the user is removed from the Veritas Application Portal, but not removed from the Velocity Console.
The following table describes each of the roles that is available in Velocity.
Table: Velocity roles
Role
How the role is assigned
Description
Velocity administrator
When an organization is created in the Veritas Application Portal, the initial user is created as a Velocity administrator.
Only Velocity administrators can assign additional users to the Velocity administrator role.
Each organization has at least one Velocity administrator who oversees all users and data in the system. This includes creating, listing, editing, and deleting users, and managing Velocity Storage Servers. The Velocity administrator can access all dialogs in the Velocity Console and can view all sandboxes, database sources, and database copies.
Velocity requires at least one Velocity administrator. You cannot remove all of your organization's users from this role.
Only Velocity administrators can set up the Velocity Storage Server or instances of the Velocity Client.
Database administrator
The Velocity administrator assigns users to this role.
A database administrator manages databases and configures who can access them.
The database administrator creates database sources in Velocity by adding databases. When a database is added, the database administrator becomes the owner of the database. The database can now be ingested.
Only one database administrator can own a database. Group ownership of a database is not available.
After the database is ingested, the database administrator can use a role to grant users access to the database source. Users with the appropriate permissions can create sandboxes from the database source. The database administrator can use multiple roles to define the groups of sandbox users that are authorized to access specific databases.
Database administrators can:
View all Velocity users in Users.
Add users.
Create roles for sandbox users in Roles, and then add users to the role. They can remove users from a role or delete it.
Add, view, edit, or delete any database sources that they own in Database Sources.
View all entries in Velocity Storage Server.
View or delete sandboxes that they create in Sandboxes.
Sandbox user
The Velocity administrator or the database administrator assigns users to this role.
A sandbox user has access to specific databases and database copies. Sandbox users can create sandboxes based on the databases that are available to them.
Sandbox users can:
View all entries in Velocity Storage Server.
View or delete sandboxes that they create in Sandboxes.
Searching...
