Falcon Deploy (FD) has been designed and built from an analyst/developer/DBA perspective, and therefore Users are the foundation of Falcon Deploy application. We set out to make an application that would make database change deployments easier, simpler, smarter and faster for the user. The application eases the deployment workload of DBAs. In the process, it empowers developers to deploy and test quicker. On the whole, Falcon Deploy makes the database change deployment and management process efficient for the user.
Administrators of Falcon Deploy create users in the application. Upon user creation, F-D sends a welcome email to the email address used during the ID creation. The welcome email has a link to the password page where the user can set their password. Upon setting a password, F-D encrypts and stores the user’s password in the database. Your email address is the user id to log-in to the application.
The welcome email also has the user’s MFA secret key. Falcon Deploy uses Multi Factor Authentication (MFA) to enhance security.
When a new person joins the organization, and becomes part of a team, he or she can be directed to the login page to request access to the application. The login page has a ‘Request Access’ button that leads you to a form that a user can fill and submit to request access to the application. Upon form submission, Falcon Deploy notifies the administrators of this request. This functionality enables a user to send a sign-up request directly from the application. Users cannot sign-up by themselves. An administrator has to create a user.
There are four types of user roles in Falcon Deploy. Users are assigned a role during creation. This role can be changed any time after creation. A user at any time has one of four roles.
Super Admin, who is also an administrator is the first user in the application. It is the super admin that installs and configures the application in your organization. This user can create other admins and users. This user has privileges to all the functionalities in Falcon Deploy.
Super Admin is comparable to the root user in Linux.
Admin users are other administrative users along with super admins. Super admin creates admins. This user has privileges to all the functionality in Falcon Deploy except making changes to the super admin users.
Consider super admin and admins as analogous to a user with ‘DBA’ role in an Oracle Database. We recommend DBAs to be the administrators of F-D since it involves configuring databases and schema credentials. Usually, DBAs manage database and schema configurations.
A User is typically anybody who is not an administrator. This user role is the most common in a usual environment setup in Falcon Deploy. It can be developers, analysts, project managers, and team managers to name a few.
This role is assigned to a user to manage a team. We recommend this role for team leads who oversee one or more projects. The role has privileges to add or remove users from a team thereby reducing dependency on administrators. Team Admin has to be part of a team to make changes to that team.
You can access User functionality from the left sidebar in the application home page.
Clicking on Users, opens the list of users in the main content area.
This functionality is available to administrators. Click on the New User button found on the top right corner of the main section. On the ‘Create User’ page, fill and submit the form to add a new user. Use the drop down to select the user role. Choose between SUPER_ADMIN (available to SA only), ADMIN, TEAM_ADMIN or USER.
If the created user is assigned a USER or TEAM_ADMIN role, an additional section opens with the following options.
- Teams ‐ Search for an existing team to add the user to the team.
- Direct Grants ‐ Search for an existing application repository to grant READ ONLY or READ & WRITE privilege on the repository to the user.
- Role Grants ‐ Search for an existing role to grant to the user.
Use the edit icon from the user list page to access the UPDATE USER page. You can update the fields added during user creation. You can enable or disable a user using the ‘Status’ field.
Since user-generated content is relative even when a user leaves the team, changes role or organization, we only soft delete a user in F-D. Use the ‘Status’ field in UPDATE USER page to mark a user as INACTIVE.