Access Management AI

It controls who can see and do what in Odoo — menus, apps, models, records, fields, views, buttons, reports and chatter — with no-code access rights, record rules, security roles and optional AI drafts.

No. Point-and-click forms cover Rules, Roles, Groups, Mass Assignment, Import/Export and user controls. Optional AI drafts a starting rule/role for review.

UI hiding is presentation. Use Create / Edit / Delete and record domains for server-enforced boundaries.

Menus, models, fields, views, UI elements, reports/actions, search, chatter, schedule, roles, access groups, AI, import/export, audits, dashboard, requests, tags, transfer, password expiry, systray, block apps and more — in one package.

Yes — Odoo 19 Community and Enterprise on Odoo.sh and on-premise. Third-party Apps Store modules are not available on Odoo Online. Multi-company supported.

Yes. The module uses Odoo’s standard translation system for its menus, views, field labels, buttons, notifications and access-management messages. Translation catalogs are included for Arabic, German, Spanish, French and Simplified Chinese. Install and activate the required languages in Odoo to use them.

OPL-1 · 90 days free support. Email nexgensolutionsodoo@gmail.com.

It can draft access rules and reusable security roles from a plain-language description, helping administrators start faster. Review and adjust the result before applying it.

No. AI is an assistant, not an approval system. It generates a draft for an administrator to review, edit and explicitly save.

The module includes AI workflows for supported configured providers such as Gemini, Claude, OpenAI and Cursor Agent. Availability depends on your configured integration and credentials.

Yes. Model permissions can be configured independently for Create, Edit and Delete, with optional record-domain rules for more precise boundaries.

Yes. Define read, write, create and delete behavior with domains, including environment-user conditions and company-specific rules where applicable.

Yes. Field rules support invisible, read-only and required behavior, with conditional options and control over relational links and Create / Create & Edit choices.

List, Form, Kanban, Calendar, Pivot, Graph, Gantt, Map, Activity and Hierarchy views can be controlled per model and targeted user or group.

Yes. Use UI element rules to hide buttons, smart buttons, notebook tabs, field elements and kanban links, with selector and conditional options.

Yes. Restrict reports plus window, server, client and URL actions, including global controls for Print and Action menus.

Yes. Import, Export and Spreadsheet actions can be controlled globally or for selected users, models and fields.

Yes. Search controls include filters, group-by, favorites, search panels and custom filter or group options.

Yes. Control messages, log notes, activities, followers, attachments and other Chatter capabilities at the level supported by each rule.

Security Roles are reusable permission packages that can be nested, assigned to users or groups, tagged, scheduled and given validity dates.

Yes. Mass assignment and Access Groups help apply roles or rules to multiple users, groups and companies efficiently.

Yes. Rules can use active dates, daily time windows, timezones and scheduled processing for time-bound access.

Yes. Rules and assignments can be scoped to selected companies, helping keep permissions aligned with multi-company operations.

Yes. The module includes controls for internal and portal access scenarios, subject to the Odoo model and security context involved.

Review login events, failed logins, access audits, rule activity and related records through the audit views, dashboards and reports.

Yes. Access Requests provide a workflow for requesting and reviewing permission changes instead of handling every request informally.

Yes. Global read-only controls can prevent users from modifying protected data while allowing the access scope you configure.

Yes. User security includes prevent-login controls and session termination options where supported by the configured security policy.

Yes. Administrators can disable developer mode for selected users and restrict module installation, upgrade and uninstallation operations.

Yes. Systray visibility can be restricted for supported items such as shortcuts, help and account-related entries.

Yes. Configure password expiry behavior, reminders and related scheduled security actions from the module settings.

Yes. Export and import JSON profiles to transfer access-rule configurations between compatible Odoo databases, then review mappings after import.

Yes. Use dashboards, pivot and graph analysis, access reports, role reports and request reports to review your security posture.

Some interface changes take effect after navigation or refresh, while server-side enforcement applies at the relevant request boundary.

Yes. Start with a limited user, group or company scope, review the resulting UI and audit behavior, then expand the assignment when verified.

Yes. Existing configurations can be reviewed and edited in the rule workspace, and compatible JSON profiles can be imported for further adjustment.

Yes. The primary workflows are no-code forms and settings. Technical customization may still be appropriate for unusual business requirements.

Check the rule status, user or group assignment, company scope, dates, priority and target model or view. Review the audit and missing-data logs when available.

Only AI workflows configured by your administrator may communicate with an external provider. Review your provider settings, credentials and organization policy before enabling AI features.

When AI generation is used, the module sends the administrator's prompt and the module's access-rule or security-role schema to the selected provider (Google Gemini, Anthropic Claude, OpenAI or Cursor). It does not send Odoo records automatically. Enable the administrator consent setting only after reviewing the selected provider's privacy and retention terms.