This guide explains the configurations that can be done after importing repositories.
Organization settings include defining your company details the first time access to Valven Atlas is defined.
In the company settings, while it is possible to define the company information, it is also possible to define the working days and hours to correlate your data on development behaviors more accurately.
With the timezone selection, the data will be represented in the local timezone to eliminate any confusion.
The configuration you applied on the organization page enables us to provide better and more related insights into the working habits of your teams.
It is also important to define a system admin to handle the integrations, reflect team workflows and manage the system for better results and assign responsible users with different permissions.
We have a flexible architecture to define organizational hierarchy where each user can see the related context to their responsibilities.
The admin can send an activation link to activate each user's account and through this activation, the admin and other users can define their password to log in to the system.
The system users can also be disabled or deleted permanently to remove the user's access to Valven Atlas.
Different user profiles in a company can have different permission settings to monitor or manage various capabilities of Valven Atlas.
The permissions can be divided into two categories; insight permissions to check the different types of reports and operational permissions to manage the system capabilities.
While the operational permissions can be provided as read-only or read-write, it is also possible to define the pages that any user can access.
This creates a flexible architecture for the system manager to distribute the management and monitoring to sub-users. As an example, one user may have access to see the integrated systems while another user can also have the authorization to delete an integration to purge the data in Valven Atlas.
Including users in Valven Atlas to include them in analysis can also be given to each team member to define their teams and track the improvements.
The contributors are the team members included in the system for the analysis. Therefore, contributors are automatically retrieved from the Git or issue repositories with their name and email address.
After the metadata is analyzed, the contributor list will be presented for the admin to select the contributors and include them in the system. Based on the active package, the number of contributors can be included in the reports.
The contributors can be activated or deactivated in this list at any time.
In various cases, it is a common scenario to see the same contributor identified in the Git provider system because of email changes, name differences, etc.
There should be a mechanism to identify such contributors and understand that they are the same person. The entities pointing to the same contributors can be selected and merged in the contributor management screen.
When these users are merged together, Valven Atlas will act as if they are the same person to provide more accurate and related results.
The teams that contributors work collaboratively in can be created and managed on the team page of settings in order to categorize insights and progress based on these teams.
The teams in the system are listed on this page and new teams can be created. Additionally, team editing and deleting actions can be done in this list.
The team additions can be handled by defining the teams manually or importing them from the repositories automatically.
If the teams are defined in the Git or issue repository providers, it is also possible to use the same teams and defined users directly in Valven Atlas.
For the companies not utilizing the team definitions in repository providers, team creation can be handled manually. Team names and users in the team can be added manually in a one-by-one or bulk fashion.