The UrbanCode Velocity security model is organization- and team-based. The organization is the base element; teams belong to organizations. Team members manage releases, events, and deployments. Administrators manage teams and assign users to them.
The team-based security model means that teams manage releases, reports, pipelines, events, and run deployments. Only team members can create or modify team-managed objects. Users can be assigned to more than one team. Users are identified by email address. The UrbanCode Velocity administrator manages the security system and manages teams and users.
After UrbanCode Velocity is integrated with HCL UrbanCode Deploy, UrbanCode Deploy teams and applications can be imported into UrbanCode Velocity. When a team is imported, all team members are imported. Users are identified by email address. Administrators can also create users.
- Roles and permissions
A number of roles are defined in the product that can be assigned to a user or group. Roles set boundaries on activities that a user or group member can perform.
- Managing users and authentications
Use User authorization and User authentication to manage users and authentication.
- Managing user groups
You can combine users into groups. When you grant permissions to the group, you simultaneously grant them to the group members. When you assign a group to a team, all group members are simultaneously assigned to the team.
- Managing teams
To prepare a team, you create the team and then add users or user groups to it. After you add users, you assign permissions to them.
- Managing user permissions
Permissions define the scope of user actions. Administrators assign users to roles when they are added to teams. Users inherit the permissions to the role. Users can have different permissions for different teams.
- Managing UrbanCode Deploy teams
When an UrbanCode Deploy team is imported, in addition to the roster of team members, all applications that are managed by the team are also imported. Imported applications can be used in any deployment that is managed by the team.
- Password management
Password management details how you can change the administrator password and retrieve the RabbitMQ password from Kubernetes and OpenShift.
- Managing user access keys
Create a key that you can use to authenticate API calls.
Parent topic: Administrating