| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Discuss (mail) • Employees (hr) • Invoicing (account) • Project (project) • Purchase (purchase) • Sign (sign) • Website (website) |
| Lines of code | 9294 |
| Technical Name |
employee_portal_suite |
| License | OPL-1 |
| Website | https://absar-alomran.com |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Attendances (hr_attendance)
• Discuss (mail) • Employees (hr) • Invoicing (account) • Project (project) • Purchase (purchase) • Sign (sign) • Website (website) |
| Lines of code | 9294 |
| Technical Name |
employee_portal_suite |
| License | OPL-1 |
| Website | https://absar-alomran.com |
| Versions | 18.0 19.0 |
Employee Portal Suite creates a complete self-service employee environment inside the Odoo portal at /my/employee. Employees can submit requests, track approvals, manage material requisitions, clock in/out with GPS enforcement, sign documents, and read company announcements â all without backend access.
ð Full Documentation
https://kinan-absar.github.io/absar/memos/employee_portal_suite_docs.html
https://kinan-absar.github.io/absar/memos/employee_portal_suite_docs.html
|
13
Request types
|
5
Employee request stages
|
6
Material request stages
|
11
Security groups
|
Key Features
|
ð Employee Requests
Multi-level approval workflow (Manager â HR â Finance â CEO) for 13 request types. Each stage sends email notifications and logs the approver, timestamp, and comment.
|
ð¦ Material Requests
6-stage procurement workflow linked to employee projects. Tracks quotations, PO status, supplier invoices, and receipt uploads through to accounting sign-off.
|
|
ð GPS Attendance
Geofenced check-in/check-out via the browser Geolocation API. Per-location configurable radius, Haversine distance validation, auto-checkout cron at 23:50 Riyadh time, and out-of-range HR notifications.
|
âï¸ Document Signing
Pending Odoo Sign requests surface on the employee portal dashboard at
/my/employee/sign. Employees complete signatures without backend access. |
|
ð¢ Announcements
Portal announcement banners managed from the backend. Supports rich-text content, date ranges, display order, group-based visibility targeting, and color-coded alert types.
|
ð 11 Security Groups
Granular roles: Employee, Manager, HR, Finance, CEO, Admin, Announcement Manager, Attendance Only, and project-specific Material Request approver roles (Purchase Rep, Store Manager, Project Manager, Director).
|
Portal URL Routes
| Route | Description | Access |
|---|---|---|
/my/employee |
Main portal dashboard | All portal users |
/my/employee/requests |
My employee requests list | Employee group |
/my/employee/material-requests |
My material requests | Employee group |
/my/employee/approvals |
Manager approvals center | Manager + roles |
/my/employee/attendance |
GPS check-in / check-out | Attendance group |
/my/employee/sign |
Pending document signatures | All portal users |
Employee Request Workflow
Requests follow a 5-stage approval chain. Each transition sends email notifications and creates Odoo activities for the next approver.
Draft
â
Manager
â
HR
â
Finance
â
CEO
â
Approved â
Supported request types:
ð Leave Request
ð Housing Allowance
ð° Salary Advance
âï¸ Business Travel
ð Training Request
ð¥ Medical Reimbursement
ð´ Vacation Settlement
ð» Asset / Equipment
ð Letter Request
ð¦ Bank Account Change
ð Position Transfer
ðª End of Service
ð Other
Material Request Workflow
Material requests are linked to the employee's work location project and pass through 6 stages with project-specific approvers.
Employee
Draft
Purchase Rep
Purchase
Store Mgr
Store
Project Mgr
Proj. Mgr
Director
Director
CEO
CEO
Final
Approved
Store Manager and Project Manager approvals are project-specific â approvers only see requests belonging to their assigned project. Quotation uploads, PO tracking, and post-approval accounting document submission are all handled directly from the portal.
GPS Attendance
|
How it works: The browser requests the employee's GPS position. The server uses the Haversine formula to measure the distance from the work location center. If Check-outs from outside the radius are allowed but flagged with |
|
Security Groups
| Group | Technical ID | Purpose |
|---|---|---|
| Employee | group_employee_portal_employee |
Submit requests; view own records only |
| Manager | group_employee_portal_manager |
Approves stage 1; sees subordinate requests |
| HR | group_employee_portal_hr |
Approves stage 2; reads all HR data |
| Finance | group_employee_portal_finance |
Approves stage 3 |
| CEO | group_employee_portal_ceo |
Final approval for both request types |
| Admin | group_employee_portal_admin |
Full CRUD on all records, settings |
| Attendance Only | group_attendance_only |
Redirected straight to attendance page; no other portal access |
| Purchase Rep | group_mr_purchase_rep |
Material request stage 2 approval |
| Store Manager | group_mr_store_manager |
Stage 3 â project-specific |
| Project Manager | group_mr_project_manager |
Stage 4 â project-specific |
| Projects Director | group_mr_projects_director |
Stage 5 approval |
Automation & Scheduled Actions
|
â° Daily Auto-Checkout Cron
Runs at 20:50 UTC (23:50 Riyadh time) â closes all open attendance records from that day. Unlike Odoo's built-in cron, this applies to employees with no work schedule (portal-only users). Auto-closed records are flagged with auto_checked_out = True.
|
ð¨ Outside-Location Checkout Alert
Automated Action (base_automation) that fires immediately when checkout_outside_location flips to True. Posts an internal chatter note on the attendance record, visible to HR in the backend.
|
Notifications Summary
| Trigger | Notified | Method |
|---|---|---|
| Employee submits request | Direct manager | Email + Odoo activity |
| Manager approves | All HR group users | Email + Odoo activity |
| HR approves | All Finance group users | Email + Odoo activity |
| Finance approves | All CEO group users | Email + Odoo activity |
| Final approval / rejection | Original requester | Email notification |
| Outside-location checkout | HR (internal) | Chatter note on attendance record |
| Auto-checkout by cron | HR (internal) | Chatter note on attendance record |
Module Dependencies
base
web
portal
hr
mail
hr_attendance
base_automation
website
purchase
sign
project
account
Configuration Notes
â¹ï¸ Employee â User link required: Each employee must have a Related User set in their HR Settings tab. Without this link, portal redirects and approval notifications will fail.
â ï¸ Attendance Only group: Users with
group_attendance_only are always redirected to /my/employee/attendance and cannot access any other portal section. Assign only to clock-in/out-only workers.
â
GPS safety fallback: If
geo_latitude and geo_longitude are both 0, geofencing is bypassed even when geo_enforce = True â preventing accidental lockouts during initial setup.
â¹ï¸ Material request routing chain: Employee â Work Location â Project â Store Manager / Project Manager. All three links must be configured for the approval chain to function correctly.
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