Easy to maintain to save your time
The tool allows to configure as many roles for a single user as you need: it let fully reflect your organizational structure.
Screenshots
Assign roles for users to automatically apply security rights
![Roles on a user form](/web/image/12028/user_formview.png)
Each user might have multiple roles
![User tree view with security roles](/web/image/12030/users_tree_view.png)
Simple to start
Besides, the tool let you create roles based on existing users. To that end just push the button 'Create role' on this user form view.
You are not obliged to assign a role for each one. For specific cases it is possible to leave the field empty and select security groups manually.
Screenshots
Combine security groups in roles for repeated use
![User role and security rights](/web/image/12029/user_role_formview.png)
Reflect your own organizational structure in user roles
![Roles' lists](/web/image/12031/user_roles_tree_view.png)
Safe and comfortable in changing environment
Rights to configure user roles are the same as for configuring users.
Frequently Asked Questions about Security User Roles Odoo v.13
If a user does not have roles at all, Odoo would work in a standard way as if the app is not installed at all. So, you should assign user groups by yourself. Such approach might be suitable for some special users such as Odoo admins.
When a few user roles are assigned for a user, all its security groups would be applied to that user, For example, if the role 'Dev/Helpdesk' has the group 'Show SLA Polciies' & 'Use Subtasks', and the role 'Sales Assistant' has the group 'Advanced Pricelists', then a user with the both roles would have the all of the rights 'Show SLA Policies', 'Use Subtasls' and 'Advanced Pricelists'.
To that end you should apply 2 actions:
1. Create a user role with the user group/access level that you need, or add them to an existing user role
2. Add the role to target users.
Afterward, when a new access right is added or removed, the related changes would be applied to all users related to the role.
If you add this role to a new user, all user groups of the role will be added to this user as well.
If a user has roles, but you manually have added a security group the latter group would not be cleared out immediately. However, it would be cleared when you add/remove roles or change any of those roles groups. So, never add user groups manually if a user has roles. The app assumes that a user has only user groups which relate to his/her user roles.
According to the current Odoo Apps Store policies:
- every module bought for version 12.0 and prior gives you access to all versions up to 12.0.
- starting from version 13.0, every module version should be purchased separately.
- disregarding the version, purchasing a tool grants you a right to all updates and bug fixes within a major version.
Take into account that the faOtools team does not control those policies. For all questions, please contact the Odoo Apps Store representatives directly.
The easiest approach is to use the Odoo store built-in workflow:
1. Open the module's page and click the button Deploy on odoo.sh
2. After that, you will be redirected to the GitHub page. Login to your account and click 'Create a new repo' or use the existing one. Please, make sure, that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project
3. Then, go to odoo.sh and click on the deploy button, submit the decision in the pop-up window and click 'Continue'. The action will trigger the installation process.
These steps would install the app for your project production branch. If you wanted to deploy the apps for other branches or update the module, you should undertake the following actions:
1. Upload the source code for the app from the Odoo store
2. Commit the module to a required GitHub repository. Make sure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add by default some crucial items there (e.g. /lib). You should upload all module directories, subdirectories, and files without exceptions
3. Deploy a target branch of the odoo.sh project or wait until it is automatically built if your settings assume that.
Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;
Re-start the Odoo server;
Turn on the developer mode (technical settings);
Update the apps' list (the apps' menu);
Find the app and push the button 'Install';
Follow the guidelines on the app's page if those exist.
Yes, sure. Take into account that Odoo automatically adds all dependencies to a cart. You should exclude previously purchased tools.
A red/orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard Odoo module tests compare final price to standard algorithm.
So, first of all, please check deployed database features. Does everything work correctly?
If you still assume that warning influences real features, please contact us and forward full installation logs and the full lists of deployed modules (including core and third party ones).
No, we distribute the tools only through the official Odoo apps store
Regretfully, we do not have a technical possibility to provide individual prices.
No, third party apps can not be used on Odoo Online.
Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.
The price for our modules is set up in euros. The Odoo store converts prices in others currencies according to its internal exchange rate. Thus, the price in US Dollars may change, when exchange rate changes.
Bug reporting
In case you have faced any bugs or inconsistent behavior, do not hesitate to contact us. We guarantee to provide fixes within 60 days after the purchase, while even after this period we are strongly interested to improve our tools.
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
Please include in your request as many details as possible: screenshots, Odoo server logs, a full description of how to reproduce your problem, and so on. Usually, it takes a few business days to prepare a working plan for an issue (if a bug is confirmed) or provide you with guidelines on what should be done (otherwise).
Public features requests and module ideas (free development)
We are strongly motivated to improve our tools and would be grateful for any sort of feedback. In case your requirements are of public use and might be efficiently implemented, the team would include those in our to-do list.
Such a to-do list is processed on a regular basis and does not assume extra fees. Although we cannot promise deadlines and final design, it might be a good way to get desired features without investments and risks.
No phone number or credit card is required to contact us: only a short email sign up which does not take more than 30 seconds.
The technical core to synchronize your cloud storage solution with Odoo
245€The tool to build deep and structured knowledge base for internal and external use. Knowledge System. KMS
298€The tool for time-based service management from booking appointment to sale and reviews
The tool to automatically synchronize Odoo attachments with OneDrive files in both ways
394€The tool to automatically synchronize Odoo attachments with Google Drive files in both ways
394€The tool to plan, share and control shifts in a form of weekly time tables
148€The tool to add new fields for Odoo contacts without any technical knowledge
38€The tool to keep complete and easy-reach employees' contact information
88€