Users

Users

In TeamTracks, users are classified into two types based on their access and functionality within the system:

1. Agents – These users have access to the Agent Portal, where they can manage objects, perform process workflow tasks, and administration if granted the necessary permissions.

2. Clients – These users access the Client Portal, which provides a set of features designed for external users, such as customers or partners.

Key Features

• When adding a new user, Admins decide whether the user will be an Agent or a Client.

• Users are independent of Tracks, meaning simply creating a user does not grant access to any features.

• Creating a user only generates their profile and login credentials. Users must be assigned to user roles to gain access to different tracks and their elements.

• The email address serves as the username, and the password is set by the Admin or the system depending on how the user is created.

📒 Note

Instead of manually managing users, use automated actions to create, update, and delete agents and client users separately. For large-scale management, it is recommended to set up a separate track and automate user handling.

User Roles

In TeamTracks, roles are used to define and manage access privileges for users. Access to Tracks and other features is determined by the roles assigned to users, not by the configuration of the user account itself. Once permissions are configured for a role, you can assign that role to different users, enabling them to access and perform specific actions based on the role's visibility and permissions. This makes user permissions easy to manage and consistent across the organization.

Types

Roles in TeamTracks are classified into two categories, similar to user types:

1. Agent Roles

• Assigned to Agent Users who access the Agent Portal.

• Agent roles define permissions related to Tracks, dashboards, lists, and other administrative features.

• Agent roles can be of two types:

  • RW (Read-Write): Provides full access to create, modify, and manage data.

  • RO (Read-Only): Restricts the user to view-only access, preventing any modifications.

2. Client Roles

• Assigned to Client Users who access the Client Portal.

• Client roles control access to Tracks, pages, and various elements in the Client Portal.

• These roles allow you to manage permissions specific to client-facing operations, ensuring that client users only see and interact with the data relevant to them.

Key Features

• Roles are essential for defining and managing what actions users can perform and which Tracks they can access.

• Users can be added to multiple roles, allowing them to have different levels of access based on the roles assigned.

• Properly assigning roles ensures that users have the right level of access without compromising security or data integrity.