Mail Activity Manager
Control visibility of activity buttons (Cancel / Edit / Mark Done) per activity type — and run server actions the moment an activity is marked done.
Who acts on an activity,
and what happens when they do.
Mail Activity Manager extends Odoo's native activities so the Cancel, Edit and Mark Done buttons can be shown or hidden per activity type, based on who created the activity and who it's assigned to. It also lets you attach server actions that fire automatically when an activity is closed — bound to the very document the activity lives on — identically from the Chatter, the popup, and the Schedule Activity wizard.
Per-Button Visibility Control
Decide who sees the Cancel, Edit and Mark Done buttons on each activity type — everyone, only the creator, only the assignee, or both.
Read-Only View for Everyone
Users who can't act still get a read-only View button in the Chatter, keeping activities transparent without granting write access.
Server Actions on Mark Done
Chain server actions to an activity type so a single Mark Done updates the record, notifies a user, or opens a wizard — no custom code.
Control and automation,
on every activity.
Seven capabilities that decide who can act on an activity and what happens when they do.
Per-Type Button Visibility
Three independent settings — Cancel, Edit and Mark Done — each choosing between All, Both Created & Assigned User, Created User, or Assigned User.
Universal Read-Only View
Users who can't act on an activity get a View button that opens it read-only. The activity is never hidden — only its action buttons are restricted.
Server Actions on Done
Attach server actions under Done Server Actions. When an activity is marked done they run in sequence, each bound to its document as record / records.
Follow-Up Actions Everywhere
If a Done action returns a wizard, notification or redirect, the module replays it. Notifications stack; wizards and pages open in order — from any entry point.
Consistent Across Entry Points
Button rules and Done actions apply uniformly in the Chatter widget, the popup form, and the Schedule Activity wizard — including the schedule-and-mark-done shortcut.
Hide Activity Types in Schedule
Flag a type as Hide in Schedule Activity to keep it out of the wizard's selection — and never auto-selected as the default — while it stays usable everywhere else.
Hide Activity Plans in Schedule
The same flag is available on activity plans, keeping internal or deprecated plans out of the scheduling wizard without deleting them.
Configured on the activity type
Everything lives on the activity type form under Settings → Technical → Email → Activity Types.
Enable Developer Mode
Server-action setup is shown to Technical / System users.
Open Activity Types
Go to Settings → Technical → Email → Activity Types.
Set Button Visibility
Choose who sees Cancel, Edit and Mark Done, plus schedule visibility.
Add Done Actions
Add server actions under Done Server Actions and drag to order them.
See it in action
Configuring the activity type, and a server action running on Mark Done.
Put it to work
Three common workflows, from access control to automation.
Restrict who can act on an activity
Lock down the Cancel, Edit or Mark Done buttons so only the right people can close or change an activity.
Run server actions when an activity is done
Turn Mark Done into an automated step that acts on the linked record.
Keep types and plans out of the schedule wizard
Declutter the Schedule Activity wizard without deleting anything.
Questions, answered
Quick answers to the most common questions.
Who sees the read-only View button?
Any user not permitted to act on an activity — based on the type's visibility settings — gets the View button in the Chatter, which opens the activity read-only. It's always available, so activities stay transparent to everyone.
Do the visibility rules apply outside the Chatter?
Yes. The Cancel / Edit / Mark Done rules are enforced in both the Chatter activity widget and the activity popup form, so users can't bypass them by opening the activity a different way.
Where do Done server actions run, and what do they act on?
They run whenever an activity is marked done — from the Chatter, the popup, or the schedule wizard. Each action is bound to the document the activity is linked to, available as record / records, and they execute in the configured sequence.
Can one activity type run different actions for different outcomes?
The base module runs a single Done bucket of server actions. Splitting behaviour into separate outcomes (for example Approve vs Reject) is provided by the companion Mail Activity Approval module, which builds on this one.
Does hiding an activity type delete it or break existing activities?
No. Hide in Schedule Activity only removes the type (or plan) from the Schedule Activity wizard. Existing activities and any other usage are completely unaffected.
Release history
A clean record of every release.
Bytesraw
🛠️ Need help?
Got a question, found a bug, or need a custom enhancement? Our support team responds within 24 hours on business days.
help@bytesraw.com →💼 Custom development
Need this module tailored to your workflow, or a brand-new Odoo solution? Let’s talk about your project.
info@bytesraw.com →| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 425 |
| Technical Name |
mail_activity_manager |
| License | LGPL-3 |
| Website | https://www.bytesraw.com |
Please log in to comment on this module