Odoo's list views let users drag column borders to widen or narrow a field, but that resize lives only in the current browser view. The moment a record is opened and closed, a filter is applied, the page is refreshed, or the user logs in the next morning, every column snaps back to Odoo's computed default widths. For teams that live in wide list views all day — a warehouse team scanning stock.move lines, an accountant reconciling account.move.line, a sales manager working a long crm.lead pipeline — that means re-dragging the same three or four columns dozens of times a day. Native Odoo has no per-user persistence for column widths in either Community or Enterprise; the width calculation is derived from the field type and content, and there is no standard setting, ir.config_parameter, or user preference that captures a manual resize.

We build a focused UI enhancement that closes exactly that gap. On the client side we extend the list renderer (the OWL ListRenderer component and its column-resize handler) so that when a user finishes dragging a column border, the new width is captured against a stable key built from the model, the view (view_id / action context), and the field name. On the server side we add a small model — for example ui.list.column.width — with fields for user_id (defaulting to self.env.user), res_model, view_ref, field_name, and width, plus a compute/normalization layer so out-of-range or stale values are ignored gracefully. Widths are read back when the list mounts and applied before first paint, so columns render at the user's preferred size with no visible flicker or re-layout. Persistence is per-user by design, so one person widening a column never disturbs a colleague's layout.

The technical implementation stays firmly inside Odoo's supported extension surface rather than patching core. Security is enforced with ir.model.access.csv giving each internal user read/write only on their own rows, backed by a record rule scoping ui.list.column.width to user_id = uid so the store is genuinely private per user and multi-company safe. The client persists changes through the standard ORM (via RPC), so the same preferences hold whether a user is on the web client or any interface that renders the list view. We keep the write path debounced and lightweight so a burst of resizes results in a single clean save, and we add an optional per-user "reset column widths" action for when someone wants to return a view to Odoo defaults. Everything is packaged as a clean addon with its own __manifest__.py, assets bundle registration, and version-pinned builds for Odoo 17.0, 18.0, and 19.0 (the OWL and asset-bundle differences between those releases are handled in the version we ship you).

Because this is build-to-order, you are not downloading a pre-existing marketplace app. After a short scoping call we confirm which models and views should remember widths, your target Odoo version and edition, and whether you want extras such as admin-set default layouts or export/import of preferences between databases. We then build, test on a staging copy of your environment, and hand over installable source. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); broader coverage — many models and views, multi-company record-rule tuning, admin-managed default layouts, or migration of saved preferences across databases — increases the quoted scope, and you receive a fixed quote after the scoping call before any work begins.