mail_activity_team

Purpose

Allow assigning teams to mail activities so team membership drives defaults, visibility, and scheduling.

Features

mail.activity.team: Define activity teams with leaders, members, optional model restrictions, and a helper to assign teams to existing unassigned activities.
res.users: Users can belong to activity teams, which drives defaults and powers team-based activity metrics in the systray.
mail.activity: Activities include a team field with defaults from user/model/type, synchronize the assignee when the team changes, and enforce that the assignee belongs to the selected team.
mail.activity.type: Activity types can set a default team that pre-populates the team and assignee when scheduling activities.
mail.activity.schedule: The scheduling wizard lets you pick a team and team member, auto-adjusting selections so scheduled activities respect team membership.
mail.activity.mixin: Team membership is honored in activity searches, deadline computations, and automatic scheduling, including support for forcing a team via context.
ir.actions.server: Activity server actions can enforce a specific team on generated activities and default the assignee to the team leader.
mail.activity UI: Forms, kanban, tree, and search views expose team fields, filters, and grouping to browse and assign activities by team.
web.activity_menu: The systray activity menu adds My versus Team toggles that update context and reload counts for team activities.
mail Activity frontend: Activity widgets display the assigned team alongside the user and avoid rendering errors when no user is set.