Advance User Restriction Management |Hide Menu, Submenu, Fields, Action, Reports, Tab, Link, Views |Model Restriction, Field Export Restriction, Field Restriction, Menu Restriction, Chatter Restrictionby Sonny Huynh
|Odoo Apps Dependencies||
|Lines of code||1757|
|Versions||14.0 16.0 15.0|
Sometime you would like to restrict to access some data for the particular user. The Odoo access right configuration is very complicated for the end user. With this app, you are able to restrict someone just only select the option on the simple form. Easy to hide the menu or sub menu, make the form to be readonly to someone, prevent user can export special field, so there are many restrictions which you would like to apply for your employees, and multi company supported.
Configuration:After intall this app, you have to enable "User Restriction Management" option
1. MODEL RESTRICTION.
This is a list restrictions on the model
Readonly: User cannot do any action on this model. It's applied on all views.
Hide Vide Mode: User cannot see views in this option.
Hide Create: User cannot create new record for this model.
Hide Edit: User cannot edit a record of this model.
Hide Delete: User cannot delete a record of this model.
Hide Archive: User cannot archive or unarchive a record of this model.
Hide Chatter: If model has chatter, user cannot see it.
Hide Export: User cannot export data of this model.
Hide Header Button: User cannot see any buttons on the form view header.
Hide Action Button: User cannot see any action buttons on form view, except buttons on form view header.
There are 2 action buttons on form view. If "Hide Action Button" option is selected, 2 of these buttons will be hide.
Hide Dropdown Action: User cannot see dropdown action on list view and form view.
Hide Duplicate: User cannot see duplicate action in dropdown action.
Hide Window Action: User cannot see window action in dropdown action. For example, This is list window actions of Sale Order model.
Hide Server Action: User cannot see server action in dropdown action. For example, This is list server actions of Sale Order model.
Hide Dropdown Print: User cannot see dropdown print on list view and form view.
Hide Particular Action Button: User cannot see action button that is in textbox, only type the title of button that you want to hide, and all buttons must be separated by commas.
You want to hide button "SEND BY EMAIL" and button "Button 2". This is setting for that, and result
button "SEND BY EMAIL" and button "Button 2" are hide.
Hide Particular Tab: User cannot see the tab on form view, only type the title of the tab that you want to hide, and all tabs must be separated by commas
On sale order form view, you want to hide tab "Other info" and "Customer Signature". This is setting for that, and result
tab "Other info" and "Customer Signature" are hide.
Readonly Particular Tab: User is readonly on the tab, only type the title of the tab that you want to hide, and all tabs must be separated by commas
Hide Particular Link: User cannot see the link on the form view, or kanban view, only type the title of the link that you want to hide, and all links must be separated by commas.
On Inventory Overview kanban view, you want to hide the link "Planned Transfer" and "Operations". This is setting for that, and result
link "Planned Transfer" and "Operations" are hide.
Hide Print Report: User cannot see the report in dropdown print on form view.
User cannot see "Pro-forma invoice" report
2. MODEL DOMAIN RESTRICTION.
You can set the domain to access the model's records
User "Marc Demo" has the access right "User: Own Documents Only", which means that user "Marc Demo" can only view and edit sale orders that he has created. With the sample domain above, user "Marc Demo" can also view 2 additional sale orders 'S00006' and 'S00007' which created by another user. However, please note that he can only view these 2 sale orders and cannot update or delete them, as the sample domain above only enables the "read" option.
Expression Type has two options: 'OR' and 'AND'.
If you select 'OR', it will combine Odoo's domain with your domain using the OR expression. The number of records you receive will be greater than the number of records you get when using Odoo's domain alone.
If you select 'AND', it will combine Odoo's domain with your domain using the AND expression. The number of records you receive will be fewer than the number of records you get when using Odoo's domain alone.
You also can use variable in domain
My App will replace "%user.id%" to current user id before combining to Odoo's domain. Similarly, you can input %today% and %now%.
Don't worry about "Invalid Datetime" My App will replace %today% and %now% before combining with Odoo's domain.
3. FIELD RESTRICTION.
This is a list field restrictions on the model
Readonly: User cannot edit this field.
Invisible: User cannot see this field.
Required: User must input this field.
Can Edit: Some fields on form view is readonly by default. If option is selected. User can change this field's value.For example, normally you cannot edit the sale order name.
This is setting for that, and result
And now you can edit the sale order name field.
Be careful to use this option, because if you edit readonly field that is default by odoo, may it will be affect Odoo workflow.
No Edit Create (many2One, many2Many): User cannot create or edit field many2one and many2many from the dropdown box.For example, If you don't allow user to create or edit delivery address.
No Open: User cannot see internal link on field many2one.
This is setting for that, and result
arrow icon is hide, and user cannot see dedails of field many2one
4. FIELD EXPORT RESTRICTION.
You can specify fields which you don't want user can export. For example
This configuration will prevent user export Total, Customer Reference and Order Reference field on sale order model.
User cannot find these fields on export form
5. MENU RESTRICTION.
You can specify menus or sub menus which you don't want user can access. For example
This configuration will prevent user access Sales/Reporting and Sales/Products/Pricelists menu. User cannot see these menus on their screen.
6. CHATTER RESTRICTION.
This is a list restrictions on the chatter.
Hide Tracking: User cannot see tracking messsage in chatter.
Hide Email: User cannot see email messsage in chatter.
Hide Send Message Button: User cannot send email message in chatter.
The "Send Message" button is hide
Hide Log Note Button: User cannot send log note in chatter
The "Log Note" button is hide
Hide Activities Button: User cannot create activities in chatter
The "Activities" button is hide
Hide Attachment: User cannot see or add attached file in chatter
The "Attachment" icon is hide
Hide Followers: User cannot see or add follower in chatter
The "Followers" icon is hide
Hide Following: User cannot follower or unfollower in chatter
The "Following" icon is hide
Email Support: firstname.lastname@example.org
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
- The author can leave a single reply to each comment.
- This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
- If you want to start a discussion with the author or have a question related to your purchase, please use the support page.