New User Teams Structure.

Feature Overview:

The User Teams feature introduces a new, lightweight way to group users within the Winmore platform. Unlike traditional User Groups, which are tightly coupled with template-level permissions and configurations, User Teams are designed specifically for collaboration and operational ownership.
Teams allow administrators to organize users in a flexible way - such as by region, country, or business responsibility and assign these teams for specific pricing activities at the lane-segment level and also system notifies the relevant team through a shared team email.

Business Benefit:

In complex pricing workflows, responsibility for pricing often lies with a group of users rather than an individual. 
The new user teams structure provides a simpler grouping mechanism that allows admins to:

• Organise users logically (by region, country, function, or responsibility).

• Improves collaboration by assigning work to teams instead of individuals.

• Within price inspector table, assign ownership of pricing activities at segments level (Origin, Main Freight, Destination).

• Notify the responsible team automatically when pricing ownership is assigned - reducing dependency on manual follow-ups and external communication.

• A team can be referenced outside the price inspector too, via a picker field referencing towards teams. With this option, a particular team can be made responsible to manage a particular tender completely.

Feature configuration:

The User Teams feature is controlled through a feature flag.

• Flag Name: User Teams Enablement 
  [Contact your Winmore implementation representative to request activation].

Functionality details.

Once enabled, Admin users will see a new Teams option under:
Studio > Users and Groups > Teams [alongside existing Groups].

Creating a Team

1. Click the “+” icon within the Teams section (refer below screen).
   

2. A slide-out panel opens, prompting the user to provide below details: (refer below screen).

   • Team Name

   • Team Description

   • Team Email
     
     

3. Saving the form creates a new User Team in the system.

Managing Users in a Team

1. Admins can add or remove users from a team at any time.

2. Selecting Add User opens a slide-out listing all users in the organisation.
   

3. One or multiple users can be selected together and saved.

Notification Mechanism:

1. When any particular segment (Origin, Freight, or Destination) is assigned to a team for pricing:

   • The system checks if the team has a group email configured.

   • If yes, the system triggers an automated email notification to the team.

2. The email includes complete information regarding the assignment, such as:

   • Tender details

   • Lane details

   • Segment-level assignment information

3. This ensures all team members are informed about the pricing responsibility.

Team's Assignment Table:

This table provides a consolidated summary of assignments at the team level, similar to how the existing User Assignment Table works at the individual level.

• The Team Assignment Table mirrors the behavior of the current User Assignment Table but aggregates assignments at the team level.

For more details on team's assignment table refer to this page.

Additional Details:

1. A user can belong to multiple teams at the same time.

2. Only users with the Customer Administrator role can view and configure teams, as all team setup is available under Studio.

3. Each team must have a unique name. Duplicate team names are not allowed.

4. Providing a team email while creating a team is optional but recommended. 

   • The team email must be unique and cannot be shared with another team.

   • A team email may match an individual user’s email address but cannot be the same as another team’s email.

5. If a team email is not provided, no notifications will be sent when the team is assigned for the pricing responsibilities.

Known Limitation:

1. A non-admin user will not get to know which teams he/she belongs to as non-admin user will not have access to Studio.
2. There is no notification generated to the user when that user gets added or removed from a team.
3. User cannot assign/update teams values within the price inspector via internal import.
4. Currently, teams not accessible in all the places wherever User Groups are. 
   For Example: 
   During RBAC (role-based access control) policy configuration, 
   While setting up the field level manual black-out configuration, etc.