| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 5105 |
| Technical Name |
do_school_leave |
| License | OPL-1 |
| Website | http://doincredible.com |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Community Apps Dependencies | Show |
| Lines of code | 5105 |
| Technical Name |
do_school_leave |
| License | OPL-1 |
| Website | http://doincredible.com |
School ERP — Leave
Student leave applications with a configurable multi-stage approval workflow and self-service portal.
Leave, routed and approved without paperwork
School ERP — Leave lets students and parents request student leave straight from the portal and routes every application through a configurable approval chain — Class Teacher, Coordinator and Principal — with each stage toggleable per leave type. Disabled stages are skipped automatically, and the right people are notified at every transition.
On final approval the attendance ledger is updated automatically, so leave days are reflected in attendance with weekends skipped. Optional yearly caps and half-day support keep entitlements accurate, while chatter and activities keep the full audit trail in one place.
Key features
Configurable Workflow
Toggle Class Teacher, Coordinator and Principal approval per leave type. Disabled stages are skipped automatically.
Self-Service Portal
Students and parents apply for leave, attach supporting documents and track approval status online.
Attendance Sync
On final approval the student is automatically marked on leave in the attendance ledger, with weekends skipped.
Balances & Caps
Optional per-type, per-year leave balance tracking with yearly caps and half-day support.
Notifications
In-app notifications and email templates fire at every transition, keeping applicants and approvers in the loop.
Full Backend Views
List, form, kanban, calendar, activity and search views with a status-bar workflow and chatter.
See it in action
How it works
User roles
| Role | Access |
|---|---|
| Student | Reads leave types and balances; creates and submits own leave applications from the portal (own records only, no delete). |
| Parent | Creates and tracks leave applications for their children through the portal (children’s records only, no delete). |
| Teacher | Reads configuration; reads and acts on leave applications for their company as an approval stage. |
| Principal | Full read/write on leave applications and balances, including final approval and unlink. |
| School Admin | Full control of leave types, applications and balances — the configuration owner. |
Fits the School ERP suite
Leave plugs directly into the rest of the suite rather than standing alone:
Technical information
Part of the School Management ERP Suite · Odoo 19 Community · by DO Incredible
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