Access Studio - Easy, Unified & User-Friendly Odoo Simplified Access Management
by IniyaSoft Technologies https://www.iniyasoft.com$ 248.55
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 2734 |
| Technical Name |
access_studio |
| License | OPL-1 |
| Website | https://www.iniyasoft.com |
| Versions | 15.0 16.0 17.0 18.0 19.0 |
November 2025 Special Offer!
Price dropped from 287.99 EUR to 214.99 EUR — save 73 EUR this month.
Access Studio for Odoo 19 — Control What Users See and Do
One place to set clear rules for every team: who can view, change, or access data and screens — without touching code.
No‑Code Configuration
Business users set access in minutes—no technical skills required.
Server‑Side Enforcement
Security policies enforced on the server, not just hidden in the UI.
Built to Scale
Fast, cache‑aware, and multi‑company ready for growing teams.
🎯 Unified Access Control Interface
Configure permissions and UI visibility from a single, streamlined workspace.
One dashboard. Clear rules. Confident control.
Top Use Cases
Role‑Based Access
Restrict CRUD, menus, and views by team or role to protect data.
Clean, Focused Screens
Hide buttons, tabs, and filters to reduce clutter and errors.
Safer Data Access
Use domains and field rules to show only what users should see.
Translations & Internationalization
Out‑of‑the‑box translations available for the module User Interface:
Need another language? Contact us and we’ll add it.
Module Installation
- Install and start configuring in minutes
- No coding or technical setup needed
Global Read-only Access
- Freeze edits system-wide with one switch
- Ideal for audits, training, or go-live windows
Disable Login
- Instantly revoke access for selected users/groups
- Enforce security and compliance in one click
Disable Debug Mode
- Block technical tools for non-admin users
- Prevent accidental system changes
Hide Menus (Main Menus & Sub-Menus)
- Hide Main Menus: Instantly hide top-level application menus such as Sales, Inventory, or Settings for selected users or groups — without modifying user access rights or technical settings.
- Hide Sub-Menus: Control visibility of any submenu under a main module (like Orders, Products, or Reports). Perfect for simplifying the interface and showing only what’s relevant to each role.
- Granular Control by User or Group: Apply menu visibility rules specifically to individual users or entire security groups — flexible for any team structure.
- Real-Time Application: No need to refresh or restart Odoo. As soon as the rule is saved, menus are instantly hidden from the assigned users.
- Non-Destructive Configuration: Menus are only hidden, not deleted or modified — Admins can easily re-enable visibility anytime through Access Studio.
Model Access (CRUD, Actions, Reports, Views)
- Restrict Read, Create, Edit, Delete, Archive, Unarchive, Import, Export per model: Control exactly what operations each user or group can perform on any model. You can disable record creation, prevent editing, block deletion, or restrict import/export — all without technical configuration.
- Hide Reports: Instantly remove access to print reports (like Quotations, Invoices, Delivery Slips, etc.) for specific users. Hidden reports won’t appear in the Print or Action menus.
- Hide Drop-down Actions: Control visibility of any “Action” menu items such as “Send by Email”, “Mark as Done”, or “Cancel Order”, keeping the interface minimal and role-specific.
- Hide Views (List, Form, Kanban, Graph, Pivot, Calendar, etc.): Decide which view types are visible to users. For example, allow only List View while hiding Form or Kanban for a controlled user experience.
- Hide “Edit Properties”: Restrict users from modifying field properties or technical settings within the interface — ideal for maintaining data consistency and preventing configuration misuse.
Field Access (Visibility, Editability & Relational Control)
- Make Fields Invisible: Hide sensitive or unnecessary fields from specific users or groups without modifying views or technical settings.
- Set Fields Read-only: Prevent users from editing key data fields like pricing, customer, or approval status while still allowing them to view information.
- Set Fields Required: Enforce mandatory data entry on critical fields such as Customer, Payment Terms, or Approval Date to ensure business data completeness.
- Remove “Quick Create” and “Create & Edit” on Relational Fields: Disable on-the-fly record creation from dropdowns, ensuring users select from approved and pre-configured values only.
- Hide “Internal Link” in Relational Fields: Prevent users from opening related master records directly from forms — ideal for restricting navigation and maintaining workflow focus.
- Per-Model, Per-User Precision: Apply different field rules for each model and user — giving total flexibility without writing a single line of code.
Conditional Field & Domain Access
- Dynamically control field behavior — make them Invisible, Read-only, or Required using custom conditions.
- Use Apply Attributes to define logic directly on model fields based on value domains or expressions.
- Use Apply Condition to link relational fields (many2one, one2many, many2many) and apply context-based access rules.
- For example: when Customer Type = Reseller, make Payment Terms required, hide Expiration Date, and keep Quotation Date read-only.
- Empower business users with adaptive forms — smarter visibility and cleaner data without writing a single line of code.
Domain-Based Access
- Restrict Read, Create, Update, and Delete permissions based on domains or conditions.
- Ensure each role can only access records they are allowed to see, enforcing territories, teams, ownership, or other conditional rules.
Button & Tabs Access
- Hide form view header buttons, smart buttons, and list view header buttons per role.
- Remove tabs to simplify forms for specific teams.
Search Panel Access
- Hide sensitive filters and group-by options.
- Prevent users from creating custom filters and custom groupings.
- Restrict users from deleting favorite filters.
Chatter Access
- Hide chatter completely or specific actions/icons
- Hide 'Send Message' to prevent sending messages
- Hide 'Log Note' to disable internal notes
- Hide 'Activities' panel in the chatter
- Hide Search Message icon to restrict searching past messages
- Hide Attachment icon to prevent file uploads
- Hide Followers icon to restrict viewing followers
- Hide Follow/Unfollow button to prevent changing follow status
- Keep conversations focused and confidential
Frequently Asked Questions
Does this module work with custom models?
Is technical knowledge required?
What support is included?
How does this differ from Odoo's built-in security?
Can I control field-level access?
Does it work with multi-company setups?
Can I hide buttons and tabs dynamically?
What happens to existing permissions?
Is there a performance impact?
Can I export/import access rules?
Release History
19.0.2.0.1
- Fix: reliably clear Access Studio cache after company switch in Odoo 19.
- Implementation: lightweight JS service hooks company activation to trigger server cache clear.
- Stability: no breaking changes; safe to update.
19.0.2.0.0
- Seamless Odoo 19 readiness: smoother installs and upgrades with up‑to‑date platform support.
- Cleaner user experience: removed rarely used favorites delete and follow/unfollow controls to reduce noise and misclicks.
- Clearer wording: “Edit Properties” label now consistent across the app for less confusion.
- Fewer support tickets: improved stability in action menus and module uninstall flows.
- Admin efficiency: a single toggle to hide “Edit Properties” across all forms.
19.0.1.0.0
- Initial release for Odoo 19.0
19.0.0.0.0
- Beta release for Odoo 19.0
Support & Contact
Detailed help and follow‑ups
Instant messaging support
Phone
Immediate assistance
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module