Users

Quotations and their line items.

Opportunities and their stages.

The stages opportunities move through, and which one counts as won. Separate from pipeline for the same reason inventory-config is separate from inventory: deleting the isWon stage zeroes out win-rate reporting for everyone, which is not the same decision as moving your own opportunity along.

Contact records, shared by every area.

Customer invoices. Issuing one posts a journal entry automatically.

Cost price and margin figures on quotations and confirmed sales orders, including their exports. Not what lets someone edit or approve those documents -- quotations:edit and invoices:edit (which also gates sales orders) already do that. This only controls whether cost/margin numbers are visible to them at all.

Credit notes. Issuing one posts a reversing entry.

Marketing campaigns, the content calendar, events, marketing spend and campaign attribution of leads. Edit covers creating and changing them and recording spend; approve is the review step for content, kept separate so the person who writes a post is not the one who clears it.

Products, stock levels, lots and serial numbers. Approve covers any path that moves stock in one step with no draft to review — recording a stock move, bale conversion, and receiving container items.

Movements between locations.

Inbound shipments and landed costs.

Warehouse locations and stock operation types — the structure inventory moves within, rather than the stock itself. Separate from inventory for the same reason chart-of-accounts is separate from the ledger: deleting a warehouse is not the same decision as correcting a product description.

Projects and tasks.

Logged hours against projects, tasks, and customers, and their billing/approval state.

Sending documents for signature and tracking who has signed — distinct from signing itself, which the signer (staff, customer, or an outside recipient) does without holding this capability at all.

Warranty modules and claims.

Repair orders — parts consumed fixing a unit, billable or under warranty.

Real estate brokerage deals — resale, off-plan, and rental — and their commission splits between agents. Approve is closing a deal: a one-way action with no draft to revisit, the same reason Production's approve level exists for completing an order.

Development projects, units, buyer bookings, payment plan templates, and construction milestones. Approve is marking a milestone complete — a real, dated fact that unlocks whichever buyer installments are tied to it, so it carries the same weight as any other one-way completion action in this app.

Karat/weight/making-charge pricing for gold jewellery products, and the daily gold rate used to price them. Retail sale is an ordinary invoice through the same posting every other sale uses — nothing here changes how a sale posts, only how its price is calculated.

Registered-medication and controlled-substance flags on products, and a dispensing log that genuinely reduces stock (via the same stock-move mechanism every other issue uses) rather than just recording an event. Never decides a tax category automatically — the real rule (registered = zero-rated, everything else = standard) is applied per invoice line by a person.

Design quantity take-offs (Revit schedules, ETABS material lists, hand-made sheets) imported per design model and version, compared between versions, and mapped by rules into a BOQ draft or revision. Edit covers models, imports, mapping rules and creating BOQ drafts; approve is separate because approval sets the budgeted values. No live Autodesk/CSI connection yet -- files only.

Manufacturing: bills of materials with routings, work centers, manufacturing orders, shop-floor work orders, quality checks and MRP planning. Approve is every step that moves stock or cost with nothing left to review — completing an order, unbuilding, accepting a failed quality check as a concession, and the manufacturing rules — everything before it is edit.

Support tickets and teams.

Tower rollout, in-building coverage, and hybrid power sizing projects — planning, phases, documents, and maintenance tickets. Approve covers signing off a project phase as complete, a formal acceptance record separate from ordinary editing.

Counter sales, refunds, and shift sessions. View is the sales history; edit is ringing up a sale; approve is closing a shift — counting cash and posting the over/short variance to the ledger, which is the one act here with a financial consequence somebody should be accountable for. Deliberately module-gated from the day it was declared, unlike infrastructure, which was not and had to be corrected.

Menus, tables and orders. View is order history and the menu; edit is taking an order — opening it, adding courses, sending them to the kitchen. Approve is the accountable set: voiding a line the kitchen has already cooked, cancelling a whole table, and settling a bill. Those are grouped together deliberately: each one either destroys food that has been paid for in ingredients or decides what a customer is charged, and they are the main internal-fraud surface in any restaurant till. A waiter needs edit; a supervisor needs approve.

Adding and retiring dishes and categories, setting prices (including timed prices such as happy hour), modifiers, kitchen stations, hotkeys, allergens and bulk menu imports. Kept apart from Restaurant edit because a price change decides what every later customer is charged -- a waiter needs Restaurant edit to take orders, not this.

Client requirements and procurement projects: checks, clarifications, team, questions and decisions, timeline and correspondence, and what the client sees in the portal. Approve releases a vetted requirement so its RFQ packages can go to suppliers.

Internal requests to buy. Editing means raising and submitting your own; approval happens in the Approvals inbox.

Orders placed with suppliers.

Supplier bills. Validating one posts a journal entry.

Customer receipts and supplier payments. Recording one posts immediately.

Manual journal entries — the one place an arbitrary debit and credit can be written.

Accounts and journals. Deleting an account with posted history is refused regardless of permission.

Analytic accounts and plans, fixed-asset models, budgets, and bank-reconciliation models -- configuration screens for accounting, separate from the chart of accounts and day-to-day ledger.

Trial balance, balance sheet, income statement, aged receivables and payables.

Read-only reports (trial balance, ledger, aged receivable, and similar) pulled from a connected Odoo account. Edit covers managing the connection itself and triggering a sync — view is scoped automatically to whichever Odoo company this organization is mapped to, never the raw connection credentials.

Bank accounts and reconciliation.

Staff expense claims — travel, meals, and other out-of-pocket costs. Approving decides whether one gets reimbursed.

A small set of actions more sensitive than ordinary admin work — reversing a posted journal entry, deleting an invoice (which reverses its posting rather than erasing it), and deleting a confirmed purchase order. Deliberately excluded from the Administrator preset itself (see PRESETS below) — not every admin should hold this; it is granted to a specific person as a real, individual decision, the same reasoning credit-notes:approve is withheld from the Sales preset. Confirmed directly, 29 Aug 2026.

Creating logins and setting what people can do.

Staff records and departments. Deliberately separate from Users: an employee row is not a login, and whoever administers accounts should not thereby be able to edit HR records.

Company profile, modules, numbering, tax configuration.

License renewals, visa/immigration card expiry, VAT and Corporate Tax filing deadlines, rent due dates, and other regulatory/authority deadlines.

Rename, hide, or add a shortcut to the sidebar for this organisation. Does not create new pages or data models -- every entry still points at something Mizo already has.

Readiness reporting and, later, transmission.

Every recorded change across the whole system — including user management, permission changes and settings, not only financial records. Administrator-only by default: it is in no other preset. An administrator can still grant it deliberately to a specific person, which is a real decision rather than something that happens by default.