Delegation - Out of Office Access & Approval Transfer
Zero Downtime While Away
The backup receives the delegated access groups and every pending activity the moment the delegation starts - nothing waits in an empty inbox.
Nothing to Clean Up Later
When the period ends or you revoke early, granted groups are removed and open activities handed back automatically. No forgotten permissions.
Never Over-Grants
Only groups the administrator flags "Can Be Delegated" are eligible - and groups the backup already had are never touched when it ends.
New Work Follows Too
Activities newly assigned to the absent user while the delegation runs are redirected to the backup at creation - not just the existing backlog.
Follows Your Leave Process
Link a delegation to a Time Off request: dates sync from the leave, and refusing or cancelling the leave revokes the delegation instantly.
Prove What Happened
Every grant and hand-back is logged in the chatter, and an Audit Trail button lists everything the backup did during the period.
See It In Action
A complete real run: User A goes away, User B covers, and everything is returned - every step below is from an actual test, nothing staged.
1. The administrator decides what can ever be delegated
A new "Can Be Delegated" checkbox on each access group. Here it is enabled on Sales / Administrator - only flagged groups are selectable in a delegation, so no one can hand over access the admin didn't approve.
2. Before: the backup has no Sales access
User B's access rights before the delegation: the Sales field is empty. Remember this - it comes back exactly like this at the end.
3. Confirm - the delegation starts and logs everything
One click on Confirm: state jumps to Running, the chatter records "User B received group(s) [Sales / Administrator]... from user A", and "Actually Granted Groups" tracks precisely what was added.
4. During: the backup is now Sales Administrator
Same User B, same screen: Sales now reads Administrator. Note Point of Sale was already Administrator before - the module knows that and will leave it alone at the end.
5. Someone assigns new work to the absent user...
While the delegation runs, a colleague schedules a To-Do and assigns it to User A - exactly what happens in real life when people don't know someone is away.
6. ...and it lands with the backup instead
The chatter proves it: "To-Do done (originally assigned to User B)". The activity was silently redirected at creation - no work ever piles up in the absent user's inbox.
7. Revoke any time - with a written receipt
One click on Revoke: state becomes Revoked and the chatter logs "[Sales / Administrator] removed from User B, 0 open activitie(s) returned to user A". The whole hand-back is documented.
8. After: access restored exactly as it was
User B is back to their normal Sales access - while Point of Sale Administrator, which they had before the delegation, is untouched. Surgical revert, not a blanket reset.
9. Link it to a Time Off request
Attach the delegator's leave instead of typing dates: From/To sync automatically from the approved Sick Time Off, and the delegation runs for exactly that period.
10. Leave refused? Delegation dies with it
The linked leave was refused - and the delegation revoked itself instantly. The chatter explains why: "revoked automatically: the linked time off ... was refused or cancelled".
11. Audit what the backup actually did
The Audit Trail button lists every message authored by the delegatee during the period - here a note User B wrote on sales order S00074 while covering. Real accountability, one click away.
12. Schedule ahead - it starts itself
A delegation starting tomorrow waits in Scheduled - access is NOT granted early. An hourly scheduled action starts it on the right day and expires it when the period ends, hands-free.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Time Off (hr_holidays) • Calendar (calendar) • Employees (hr) |
| Lines of code | 426 |
| Technical Name |
sm_user_delegation |
| License | OPL-1 |
| Website | https://apps.odoo.com/apps/modules/browse?author=Steven Marp |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module