Odoo's stock access model is coarse. ir.model.access.csv grants a group read/write/create/unlink on a whole model, and record rules scope which rows they touch, but neither lets you keep write access while stripping only the Create button, only the Delete action, or only the CSV/XLSX export from a list view. In practice teams need exactly that granularity: a warehouse clerk who can edit stock moves but must never create ad-hoc records, an accountant who can update invoices but must not archive or export the master ledger, a support agent who edits tickets but cannot mass-delete. When Odoo native runs out of road, most teams resort to fragile per-model view overrides or over-restrict with perm_unlink=0 and break legitimate edit flows.

Hide Create is a build-to-order Odoo module that gives you surgical, per-group control over the four dangerous UI actions, Create, Delete (unlink), Archive/Unarchive, and Export, plus Duplicate where you need it, targeted at exactly the models and user groups you specify. We drive it from a small configuration model so you manage rules from a settings screen rather than editing XML: pick a model, pick a security group, and toggle which action buttons disappear for members of that group. Under the hood we combine two enforcement layers so a hidden control cannot simply be re-enabled by a power user. In the views we inject the relevant create, delete, edit and export_xlsx option flags on the tree/form/kanban nodes (via inherited ir.ui.view arch or an fields_view_get/get_view override that adapts the arch to the current user's groups). In the ORM we override create(), unlink(), write() (for the active/archive field) and the export path so a blocked action raises AccessError even if triggered through the JSON-RPC/XML-RPC API, an imported list, or a crafted URL, closing the gap that view-only hiding leaves open.

Because every Odoo database has a different mix of models, groups and edge cases, we build this to order rather than shipping a one-size configuration. We start with a short scoping call to map which models, which groups, and which of the four actions each combination should lose, then confirm whether super-users, base.group_no_one and portal users are in or out of scope. We develop against a copy of your models, respecting your Community or Enterprise edition and targeting Odoo 17.0, 18.0 or 19.0, ship the module with its own __manifest__.py, security rules and configuration data, and validate on a staging database before touching production. Typical delivery is 2 to 4 weeks from confirmed scope depending on how many model/group combinations and non-standard views are involved.

Pricing starts from $249 (indicative, single-company base scope); wider model and group coverage, custom studio or third-party models, multi-company record-rule interplay, and deeper localization of blocked-action messages increase the quoted scope. You get a fixed quote after the scoping call, never a surprise invoice.