Base Install Request
Module installation request and approval workflow for Odoo
Base Install Request provides a controlled module installation process in Odoo, allowing users to request module installation and admins to approve before actual installation, ensuring system safety and control.
This module is useful for large organizations needing strict control over new module additions, avoiding unnecessary or conflicting modules, and tracking installation request history.
Key Features
Key points
• Request Workflow: Users submit module install requests, admins review and approve/reject
• Approval Queue: List of pending requests with module info, user, reason
• Dependency Check: Auto-check dependencies and add to request
• Notification: Email/chatter notifications when request approved/rejected
• Request History: Installation request history with status, approver, timestamp
• Bulk Approval: Admins can approve multiple requests at once
Terminology
| Fields | Trường dữ liệu | Description |
|---|---|---|
| Install Request | Yêu cầu cài đặt | User request to install module |
| Approval | Phê duyệt | Admin accepts request |
| Rejection | Từ chối | Admin rejects request with reason |
| Pending | Chờ duyệt | Request awaiting admin review |
| Approved | Đã duyệt | Request accepted, module will install |
| Rejected | Đã từ chối | Request rejected |
Module Request Process
Steps
1. User submits request: Go to Apps, find desired module, click "Request Install" instead of "Install". Fill in reason for needing module.
2. Admin receives notification: Admin gets email/chatter notification about new request. Go to Settings → Technical → Install Requests to view list.
3. Admin reviews: Admin checks module (description, dependencies, impact), reads user reason, decides to approve/reject.
4. Approve/Reject: Admin clicks "Approve" to auto-install module, or "Reject" and fill in rejection reason.
5. User receives result: User gets notification about result. If approved, module installs and is ready. If rejected, user sees reason.
6. Module installation: After approval, system auto-installs module and dependencies, updates Apps list.
Real-world Examples
Common Use Cases
| Scenario | Implementation | Benefits |
|---|---|---|
| Enterprise module control | Admin enables Base Install Request, users cannot self-install modules. All requests must go through admin approval. | Avoid unnecessary, conflicting, or unsafe modules |
| Track installation reasons | Users must fill reason when requesting. Admin reviews reason to decide. History saved for audit. | Understand user needs, assess necessity, audit trail |
| Manage dependencies | User requests module A, system auto-adds modules B, C (dependencies) to request. Admin approves entire bundle. | Ensure module works correctly, no missing dependencies |
| Reject unsuitable modules | User requests expensive/unnecessary module. Admin rejects with reason "Similar module exists" or "Not aligned with process". | Save costs, avoid system complexity |
Configuration and Permissions
Key points
• Activation: Go to Settings → General Settings → Permissions, enable "Module Installation Requests"
• User permissions: Regular users only have "Request Install" right, not direct "Install"
• Admin permissions: Admins need "Administration / Settings" to approve/reject requests
• Notification settings: Configure email templates for approve/reject notifications in Settings → Technical → Email Templates
• Auto-approve rules: Can create automated actions to auto-approve modules from whitelist
Best Practices
Key points
• Require clear reasons: Users should explain specifically why module needed, what use case
• Admin responds quickly: Process requests within 1-2 days to not block user work
• Reject with reason: When rejecting, explain clearly and suggest alternatives
• Test on staging: Admins should test module on staging before approving for production
• Periodic review: Review installed module list, remove unused modules to keep system lean