| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 235 |
| Technical Name |
cm_sa_user_offboarding_kit |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 235 |
| Technical Name |
cm_sa_user_offboarding_kit |
| License | OPL-1 |
| Website | https://cm.sa |
| Versions | 17.0 18.0 19.0 |
User Offboarding Kit
Offboard leavers on schedule and stop paying for Enterprise seats they no longer use.
When an employee leaves, reclaiming their Enterprise seat and revoking access takes a surprising number of clicks, and the easy steps get missed. Meanwhile dormant accounts keep consuming licenses, so the bill runs 20% high every month. This kit gives HR ops and IT one place to do it all: schedule a deactivation date per user, auto-flag dormant accounts, bulk-archive them, and log every step.
User Offboarding Kit
Schedule user deactivation dates, auto-flag and bulk-archive dormant users, and reclaim Enterprise seats.
What it does
When an employee leaves, reclaiming their Enterprise seat, revoking their access, and cleaning up their audit trail takes a surprising number of clicks, and easy steps get missed. Meanwhile dormant accounts keep consuming licenses and keep carrying access they no longer need.
Odoo core has no scheduled deactivation, no dormant-user list, and no bulk offboarding wizard, so HR ops and IT run their own checklists and hope nothing slips.
What this module adds:
- Schedule a deactivation date and reason on any user; a daily cron archives them on the date you set and posts the reason to chatter.
- Weekly cron flags users that have not logged in for N days (default 90) for review in a dedicated Dormant Users list.
- Bulk-archive dormant users from a wizard with a single shared reason, written to chatter on every archived account.
- System users (admin, public, portal, __system) always skipped.
- Every archive logged with user, reason, date, and source (scheduled / dormant / bulk).
- Reactivate is always one click from the user form.
Who benefits
IT admins, HR operations, and finance controllers at mid-market and enterprise companies paying per-user Odoo Enterprise licensing.
How it works
Two stored fields on res.users and two crons (daily archive, weekly dormant review). No deeper core-model surgery. TransactionCase tested on Odoo 17, 18, and 19. Safe to install, safe to uninstall.
What the module looks like
Real screenshots from a live Odoo 19 install. Every view is standard Odoo chrome, no bespoke widgets to learn.
Common questions
Does it inherit or patch core Odoo models?
_register_hook to wrap the target method at registry load, and the wrapper unwinds cleanly at uninstall. No schema changes to core tables, no monkey-patches, no Studio surgery.Does it work on Odoo Community, or only Enterprise?
Can I uninstall it cleanly if it does not fit?
What support do I get after buying?
Can Cube Master customise it for my company?
Beyond this module, Cube Master also builds:
We are a full technology house. The Odoo utility you are reading about is one part of what we ship. If your back office, website, or app team needs more, we have the team for it.
More from the Cube Master catalogue
We ship 33 single-feature utilities at the same price point. If this one solved a pain for you, the others probably will too.
About Cube Master
We blend mastery with creativity - نمزج الإتقان بالإبداع
Cube Master is a Saudi technology house based in Al-Mubarraz. We design, build, and run business systems for customers across the Gulf and beyond: end-to-end Odoo ERP rollouts, custom AI workflows, corporate websites, and mobile apps. Strategic technology partners with Microsoft, AWS, Odoo, and Umbraco.
The Odoo utility you are reading about is one small piece of what we ship. If you need any of the above for your company, talk to us.
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