Odoo SaaS QMS 3-Tier Security Setup

1. JOB POST: Odoo SaaS Security Configuration – QMS User Roles (3‑Tier Access Model)
Project Overview
We are a small company implementing a lightweight Quality Management System (QMS) inside Odoo SaaS. We need an experienced Odoo SaaS security specialist to design and configure a three‑level permission model that is clean, audit‑friendly, and fully compatible with SaaS limitations (no backend access, no custom modules, no Studio).
Required Deliverable: 3‑Level QMS Security Model
1. QMS Read‑Only (External Auditors / Inspectors)
- Read‑only access to QMS menus and documents.
- No create/edit/delete.
- No access to non‑QMS modules.
- Must avoid Portal/Public menu leakage.
- Must be safe for ISO/FDA/MHRA audits.

2. QMS Contributor (Internal Staff)
- Can create and edit QMS documents.
- No configuration or system‑level access.
- No access to non‑QMS modules.
- Must avoid unintended implied permissions.

3. QMS Manager (Quality Lead / Compliance Officer)
- Full control over QMS content.
- Can approve, archive, and manage workflows.
- Limited configuration access only where required.
- Must not gain system‑wide admin rights.
Technical Requirements
- Work within Odoo SaaS constraints.
- Build groups without unintended inheritance.
- Configure menu visibility, ACLs, and record rules.
- Prevent leakage of Portal/Public menus.
- Provide documentation of groups, ACLs, rules, and menus.
Deliverables
1. Fully configured 3‑tier QMS security model.
2. Documentation (PDF or Google Doc).
3. Handover call or recorded walkthrough.
Ideal Contractor
- Proven Odoo SaaS experience.
- Strong understanding of security groups, ACLs, record rules, and menus.
- Audit‑readiness experience is a bonus.
How to Bid
- Summary of Odoo SaaS security experience.
- Examples of similar work.
- Estimated timeline and cost.
- Questions for clarification.
Goal
A clean, minimal, safe, and audit‑ready QMS permission structure that works reliably within Odoo SaaS.