This module adds the possibility to assign teams to activities.
auto_awesome What this module does
AI-generated from the code · Odoo 19.0Lets you group users into activity teams and assign activities to a whole team instead of a single person. Team members can see and handle the team's activities, and can be notified when a team activity is created.
This module adds the concept of activity teams to Odoo's activity system. You create teams under the new "Activity Teams" menu (Activities section), giving each a name, a team leader, members, and optionally the models the team works on. A team can be archived, and a button on the team form assigns the team to existing unassigned activities that match its members and models.
- Activities can now be linked to a team (
team_id) as well as a user. When you pick a team, the assigned user is automatically set to the team leader or the only member, and Odoo blocks saving an activity whose user is not a member of the chosen team. - Activity types can have a default team, so new activities of that type are pre-filled with the team and one of its members.
- Activity plans and plan templates can use a "Team" responsible type; the template then requires a team and a team user, and scheduled activities are created for that team.
- Server actions and the schedule-activity wizard also let you choose a team, and the wizard hides the individual user field when a team is selected.
- If a team has "notify members" enabled, team members (except the assigned user) receive a notification when an activity is assigned to the team.
- The activity systray gains a "Team Activities" filter next to "My Activities", and activity views show the team, allow filtering by "My Team Activities" and grouping by team. Users can be linked to teams from their user form.
Depends on
Required by other modules
Menus it adds
Models and fields (8)
- res.users · extends an existing modelactivity_team_ids (Activity Teams)
- mail.activity · extends an existing modelteam_id, user_id, team_user_id (Team user)
- ir.actions.server · extends an existing modelactivity_team_id
- mail.activity.team · new modelname, active, user_id (Team Leader), member_ids (Team Members), res_model_ids (Used models), notify_members, count_missing_activities (Missing Activities)
- mail.activity.type · extends an existing modeldefault_team_id
- mail.activity.mixin · extends an existing modelactivity_team_user_ids (test field)
- mail.activity.schedule · extends an existing modelactivity_team_id, activity_team_user_id (Team user)
- mail.activity.plan.template · extends an existing modelresponsible_id, activity_team_id (Team assigned to), responsible_type, activity_team_user_id (Team user), activity_team_required
Text generated by AI (DeepSeek) from reading the Odoo 19.0 code on GitHub; it may contain mistakes, so check the code before deciding. The module is very large and only part of the code was read. View the code on GitHub
Availability by version
Reviewed: 2026-11-03Confirmation status: 8 confirmed, 1 with no information of 9 versions.
Sources · Odoo 19.0
Confirmed on 2026-11-03 in branch 19.0 of OCA/mail.
terminal Installation and usage
OCA documentation · Odoo 19.0Usage
Source · Odoo 19.0To set up new teams:
- Go to Settings / Activate developer mode
- Go to Settings / Technical / Discuss / Activity Teams
- Create a new Team and assign (optionally) the models in which it will be used, and the members of the team.
You can also assign a user to Activity teams going to Settings / Users & Companies / Users, and in the Preferences tab, field Activity Teams.
When you create a new activity the application will propose the user's assigned team.
When creating activity plans, instead of assigning an activity to a user, there is also the option to assign it to a team instead.
You can report on the activities assigned to a team going to Dashboards / Activities, and then filter by a specific team or group by teams.
No verified information in OCA: Installation, Configuration.
Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.
Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.