Password Manager v.16

The tool to safely keep passwords in Odoo for shared use. Shared vaults


The tool does not require extra dependencies beside standard Odoo apps.
Current version:


This app lets organize the safe passwords keeping system to structure, find and securely share password bundles.

Odoo passwords interface

Shared passwords vaults for team use

Passwords are combined in bundles: each might be shared with any user and any user group

Single view interface

Structure vault by tags and types, sort keys, proceed with mass actions, copy credentials to the clipboard from the same interface

Encrypted and protected password manager

The tool introduces a few security layers to minimize the possibility of data leaks

Portal sharing

Optionally share passwords with Odoo portal contacts

Auto generation

Force Odoo and let users create passwords based on chosen length and requirements

Passwords quality check

Password strength is estimated in real-time to make sure no weak passwords are introduced. Potential duplicates are easily detected

Batch update, export, and import

Configure the mass actions: export, update tags or linked partners, archive or restore, import vaults from an electronic table, etc.

Custom fields

Define passwords' typology and add custom attributes.

Shared use, encryption, and protection of passwords

Sharing Policies

  • To grant access for a bundle just indicate a user or a user group in the table of access levels
  • Bundle administrators may access, update or delete the bundle, its passwords, and its tags. Admins are assumed to manage access levels, modify update policies, and set extra passwords
  • Full rights users may access, update or delete passwords and tags related to the bundle, but they can't change the vault itself, its access levels, or settings
  • Readonly access users may observe and address passwords and tags of the bundle. Such users can't modify any objects
  • The bundle creator is always its administrator. The Odoo super admin (with id 1) has full rights to all bundles and passwords
  • For bundle read-only users, it is possible to additionally restrict access to specific password keys. In particular, define the groups or/and users that may see a password. A read-only user should either have one of the mentioned groups or should be among the mentioned users. If none of the fields are defined, all bundle users can access a password

Security Layers

  • Have as many password vaults for any user group as you need
  • All passwords are symmetrically encrypted. It means that to decrypt a password, plotters should know the exact decryption algorithm and a bundle decryption key/bundle salt and password
  • For each bundle, you can assign an extra password, which would be required to enter each time any user applies to that bundle or its passwords. The session period after successful login is set up in minutes
  • Vault extra password is also kept in the database decrypted, and might be changed by a bundle administrator (sure, if he/she enters a correct old paraphrase). If the bundle password is set, keys are encrypted by that password hashed by an auto-generated salt
  • For each bundle, it is possible to define password update policies in days. Then, the user who is set up as 'Responsible for password updates' would be assigned special activities to update keys.
Passwords security access levels

Portal vaults

  • Optionally turn on password sharing with portal users. To that goal, on the configuration page tick the box "Portal vaults" and add the mass action "Share in portal"
  • Within a password bundle, create an unlimited number of portal password vaults shared with an unlimited number of Odoo partners
  • Each bundle internal user can create or update any portal vault linked to this bundle. To add a password for a vault, select the required keys and trigger the mass action "Share in portal". Optionally send an invitation during sharing
  • Navigate over and manage available vaults right from the backend navigation panel
  • Define a validity date to auto-archive password vaults for a temporary sharing
  • A contact may access all vaults where he/she or his/her company is indicated in the field "Portal Access". Take into account that a user should have portal rights that might be granted from a partner form view (Action > "Grant portal access")
  • Portal users can open password vaults from the specially introduced entry in the home portal page
  • Each portal vault is obligatorily secured with a password. All keys are kept encrypted and might be decrypted only after entering the vault password. The portal session length is defined per each vault
  • By default, only a password reference, user name, and password key are shown. Optionally show an URL, phone, email, and notes
  • The tool lets portal users show/hide password keys, navigate and search by shown columns.
Mass actions: sharing
Vaults: portal view

Custom attributes for Odoo passwords

  • Custom attributes creation does not require any technical knowledge. In order to show a new property for passwords, just add a new field and enter the details
  • It is possible to add custom fields of the following types: single-line text (char), simple text without formatting (text), rich text (HTML-formatted text), integer or float numbers, drop-down choice with your own options (selection), checkbox (boolean), date or date and time, binary (a file to upload), reference to another Odoo document (e.g. for sale order, contact; many2one)
  • The tool lets you comfortably select an interface position of a custom field from a closed list of options
  • Distinguish passwords by type in order to show properties only for suitable ones. Thus, the set of columns for 'virtual servers' and 'email servers' might be different
  • Mark a custom field required to force users to enter values
  • Custom password fields might be imported and exported
  • The rights to create custom fields belong only to Odoo administrators.
Types of custom fields for access keys
Customized password form views

Duplicates detection and passwords merging

  • The app introduces a configurable system to find passwords duplicates
  • Define on your own which fields should be used to search for duplicates. Choose such fields on the app configuration page, the section 'Duplicates search'
  • As duplicate criteria use any stored field of the following types: char (reference, user name, email, phone, etc.), text (notes), many2one (linked partner, type, etc.), date and datetime, integer, and float. Duplicates detection is possible also based on custom fields of the same types
  • For all fields, a duplicate should have absolutely the same value. For example, '123' equals '123', but '123' is not equal to '1234'. Only in the case of char fields, it is a comparison without taking into account capital letters ('Server' equals 'serVER')
  • Apply the filter 'Potential duplicates' in the passwords interface to observe candidates. You may search within a particular bundle or in all passwords simultaneously
  • When you register a new password, check also the red button on the top right corner. If it is shown, make sure you do not create a potential copy of an existing key
  • Found duplicates or just any password keys might be merged into a single record. To that end, do not forget to add the mass action 'Merge passwords' on the configuration page
  • To merge passwords, select the required keys and push the mass action 'Merge passwords' on the right navigation panel
  • In the wizard, as the 'Password to merge', choose one that will be the prime source of the details. In case of conflicts, its value will be prioritized
  • In the wizard, as the 'Merged passwords', choose keys that will be used as a source of complementary details (for example, details that are missing in the main password)
  • Then, press the button 'Save'. As a result, the app will archive all the 'Merged passwords' and enrich the 'Password to merge'
  • Starting from the 'Password to merge' values, the tool will check the fields reference, bundle, user name, email, URL, phone, last password update date, and linked partner. The app will select the first found not null value
  • The app will also accumulate notes, attachments, and tags from all merged records
  • Values of custom fields will be chosen according to keys sequence starting from the 'Password to merge'. Take into account that tables (one2many and many2many fields) will be left as they are in the 'Password to merge'.
Passwords duplicates filter
Passwords merging tool
Odoo passwords duplicate fields

Configuration and Installation Tips for Password Manager Odoo v.16

Python dependencies

To guarantee tool correct work you would need a number of Python libraries: zxcvbn, cryptography:

pip3 install zxcvbn cryptography

Frequently Asked Questions about Password Manager Odoo v.16

To see all passwords of a partner, go to Contacts, open the partner and click the smart button 'Passwords'. After that, you will be redirected to the Password manager app and will see all the passwords of this partner.

The button 'Delete' was hidden from the main bundles menu for the security purpose. To delete a passwords bundle: 1. Click on the three dots button in the top right corner of the bundle 2. You will be redirected to the editing mode of the bundle, from there, click 'Save' 3. Above the passwords bundle you will see the button 'Action', click on it and choose the option 'Delete'.

According to the current Odoo Apps Store policies:

  • every module bought for the version 12.0 and prior gives you an access to the all versions up to 12.0.
  • starting from the version 13.0, every version of the module should be purchased separately.
  • disregarding the version, purchasing a tool grants you a right for all updates and bug fixes within a major version.

Take into account that faOtools team does not control those policies. By 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

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 project

3. Then, go to 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, 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 project or wait until it is automatically built if your settings assume that.

  1. Unzip the source code of the purchased tools in one of your Odoo add-ons' directories;

  2. Re-start the Odoo server;

  3. Turn on the developer mode (technical settings);

  4. Update the apps' list (the apps' menu);

  5. Find the app and push the button 'Install';

  6. 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).

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.

Odoo demonstration databases (live previews)

For this app, we might provide a free personalized demo database.

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.

By your request, we will prepare an individual live preview database, where you would be able to apply any tests and check assumptions for 14 days.

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.

You may also like the tools
Cloud Storage Solutions

The tool to flexibly structure Odoo attachments in folders and synchronize directories with cloud clients: Google Drive, OneDrive/SharePoint, Nextcloud/ownCloud, and Dropbox. DMS. File Manager. Document management system

Google Drive Odoo Integration

The tool to automatically synchronize Odoo attachments with Google Drive files in both ways

OneDrive / SharePoint Odoo Integration

The tool to automatically synchronize Odoo attachments with OneDrive files in both ways

ownCloud / Nextcloud Odoo Integration

The tool to automatically synchronize Odoo attachments with ownCloud/Nextcloud files in both ways

KnowSystem: Knowledge Base System

The tool to build a deep and structured knowledge base for internal and external use. Knowledge System. KMS. Wiki-like revisions.

Universal Appointments and Time Reservations

The tool for time-based service management from booking appointments to sales and reviews

KPI Balanced Scorecard

The tool to set up KPI targets and control their fulfillment by periods. KPI dashboards. Dashboard designer. KPI charts

198€ 168€
Joint Calendar

The tool to combine different Odoo events in a few configurable super calendars

Odoo Documentation Builder

The tool to create website documentation based on your knowledge base

436€ 430€