User Management

AIR > Settings > User Management > Users:

This section allows administrators to add new users to the Binalyze AIR platform, specifying essential details such as the user's name, organization, role, and login credentials.

1. Type:

   • This field defines the type of user being added, depending on the organization's structure. For example, it could differentiate between internal users and external users (like clients or contractors) if your organization uses different user types.

2. Name:

   • Name: The first name of the user being added (e.g., "John").

   • Surname: The last name of the user (e.g., "Doe"). These fields are important for identifying and managing users in the system, especially in larger organizations.

3. Username*:

   • The username is a mandatory field (indicated by the asterisk). This is the unique identifier that the user will use to log in to the AIR platform (e.g., [email protected]).

   • The username is often based on the user's email address to ensure uniqueness and facilitate easy recognition.

4. Email*:

   • The email is also a mandatory field. It is used for account-related communications, such as password resets, system alerts, or notifications.

   • This email should be valid and associated with the user being created to ensure they receive important platform-related information.

5. Organization*:

   • This field allows you to assign the new user to a specific organization within the Binalyze AIR system.

   • If multiple organizations are managed within the AIR platform (e.g., in the case of a multi-tenant setup), you can select which organization the user belongs to.

   • The system can restrict users from viewing or managing other organizations, depending on their access privileges.

   • Note: If no organization is selected or assigned, the user may have limited or no permissions within the platform.

6. Role*:

   • The Role dropdown allows you to assign the user's role within the platform. Roles define the level of access and permissions the user will have. Common roles could include:

     • Administrator: Full access to manage the platform, users, and assets.

     • Investigator: Access to forensic and incident investigation features.

     • Viewer: Read-only access to view data and reports.

   • This field is crucial for setting user permissions and ensuring that they can only perform actions aligned with their responsibilities.

7. Password*:

   • This is where you set the password for the user’s account. The password should meet the organization's security requirements (e.g., complexity, length).

   • A secure password is essential to ensure that unauthorized access to the platform is prevented.

8. Confirm Password*:

   • This field is used to confirm the password entered above. Ensuring that the passwords match helps avoid login issues caused by incorrect entries.