[18.0][ADD] mail_activity_restrict: Option to make activities readonly when user is not assigend#164
[18.0][ADD] mail_activity_restrict: Option to make activities readonly when user is not assigend#164CRogos wants to merge 2 commits into
Conversation
…ons based on assigned user
2cedb27 to
5877407
Compare
…stricted activities
5877407 to
2db4e6d
Compare
|
@NICO-SOLUTIONS what do you think of this? |
|
@CRogos |
|
@CRogos It might make sense to restrict editing of activities to the assigned user, and possibly also to the person who created the activity. In practice, it happens quite often that someone creates an activity for someone else and later realizes that changes are needed for various reasons. In those cases, it would be helpful if the creator could also edit it. What do you think? |
|
hmm... I understand your use case. In our case, the activity is automatically created, when an equipment is returned. Currently the creator is the person who triggers the workflow (returner), but I assume I can adapt the process that the activity creator can be changed to odoo-bot, because the returner should not be able to reset the activity. |
This module gives you the option to restrict the write access on certain activity types. e.g. if activities need to be done by certain users/teams.
When this option is activated on an activity type, and the activity is not assigned to you, the edit options are hidden.

When the activity is assigned to you, it is still visible:
