Restrict users from exporting data, printing documents, or running batch actions from the action dropdown menu in list or form views.

Control which data views (List, Kanban, Graph, Pivot, Calendar) are accessible to specific user profiles to simplify the data browsing experience.

Disable the global search bar for specific records or views to enforce strict data browsing paths and prevent unauthorized database queries.

Prevent users from creating custom filters or accessing sensitive predefined search filters (such as 'Create Date' or financial filters).

Restrict users from grouping data by sensitive fields (such as Salesperson, Margin, or Customer) in list and pivot views.

Prevent users from modifying shared favorites, saving custom searches, or altering default public search filters.

Make specific editable fields read-only for designated users or groups. Prevent unauthorized modification of critical data while allowing users to view the information.

Enforce mandatory data entry on specific fields dynamically based on user profiles or conditional rules, ensuring data integrity and completeness before saving records.

Apply read-only restrictions conditionally based on domain filters (e.g., lock the Price field only when the order status is 'Confirmed' or total exceeds $1,000).

Conditionally hide specific fields based on dynamic record domains (e.g., hide discount fields if the customer is not a VIP or if order amount is below threshold).

Restrict the selectable records available in Many2one or Many2many relational dropdown fields by applying custom domain filtering rules.

Disable 'Create and Edit', 'Quick Create', or 'Open' options on Many2one relational fields to prevent users from creating unauthorized related records from dropdowns.

Remove specific dropdown selection values or stage options from status fields (e.g., hiding 'Approved' or 'Cancelled' stage from standard operators).

Dynamically override field visual widgets, labels, or UI attributes (such as changing a dropdown to radio buttons or forcing bold/color alerts for specific profiles).

Remove specific smart buttons (such as 'Invoices', 'Delivery', or 'Sales') from the top navigation ribbon of record forms, preventing users from accessing related documents.

Disable clickable links, dropdown menus, or card actions within Kanban views, ensuring users can view Kanban cards without being able to open or modify underlying records.

Completely hide entire notebook tabs or section pages (like 'Other Info', 'Accounting Details', or 'Order Lines') within form views to streamline the UI and protect sensitive data sections.

Remove specific default or saved search filters from the search bar dropdown, preventing users from viewing specialized datasets or sensitive segmented records.

Disable specific 'Group By' data categorization options in list, pivot, and graph views, restricting users from aggregating records by sensitive dimensions like Salesperson or Customer.

Completely hide the right-hand or bottom communication Chatter section (including message history, internal log notes, and planned activities) on record forms for confidential profiles.

Instantly block specific users or profiles from logging into the Odoo instance. When a restricted user attempts to authenticate, a clear warning banner alerts them that their account has been disabled by security rules.

Restrict access to Odoo's developer and debug modes (?debug=1 or ?debug=assets). Prevents non-admin users from inspecting Technical Menu items, field metadata, view architectures, and administrative actions.

Convert an entire database model (such as Sales Orders, Products, or Customers) into strict read-only mode across all form, list, and kanban views. Instantly hides 'New', 'Edit', and 'Delete' buttons for affected users.

Completely hide an entire model and all associated application icons, menu items, action shortcuts, and relational link fields from the user's workspace, rendering the data object invisible.