Teams that run their whole business in Odoo still keep shared logins — banking portals, courier accounts, SMTP/API keys, supplier extranets, social accounts — scattered across spreadsheets, chat threads, sticky notes, and personal browser vaults. There is no controlled way to say "the finance team may see the bank credential but not the marketing API key," no record of who viewed or copied a secret, and no clean way to revoke access when someone leaves. Odoo core has no credential-vault model: res.users handles authentication and ir.config_parameter stores plaintext system settings, but neither is designed to hold, encrypt, or govern access to third-party secrets. This is exactly the road-runs-out point where a purpose-built module belongs.

ECOSIRE builds a dedicated Password Manager as native Odoo modules — a real models.Model (for example password.vault and password.entry) with fields for title, username, URL, notes, category, and an encrypted secret. Secrets are never stored in cleartext: the module encrypts the password field at rest using a server-side key held outside the database (env var / config), with @api.depends-free explicit encrypt/decrypt methods so a raw SQL dump or a casual read() never exposes the value. Access is governed the Odoo-native way: ir.model.access.csv sets model-level create/read/write/unlink per group, and ir.rule record rules scope which vaults and entries a given user or team can even see — so a group-shared vault, a personal vault, and a department vault can coexist with strict isolation. Every reveal, copy, create, and edit writes an audit row (who, when, which entry, from which IP where available), and mail.thread chatter gives each entry a change history. Backend views are standard XML/OWL list and form views with a masked secret widget and a reveal-on-demand action; an optional QWeb report can produce a controlled, watermarked access inventory for audits.

Beyond the base vault we scope the governance features your team actually needs: group-based sharing with per-entry override, automated actions (ir.cron / server actions) that flag stale or expiring credentials and notify owners, optional expiry and forced-rotation reminders, and read-only "break-glass" access patterns for emergencies. Because it is built on Odoo's own ORM and security layer, the vault is reachable through the standard XML-RPC/JSON-RPC API for controlled programmatic reads by other internal modules — under the same access rules, never bypassing them. We build against your target line — Odoo 17.0, 18.0, or 19.0 — and account for Community vs Enterprise differences (Enterprise-only widgets and features are used only when your edition supports them; on Community we ship equivalent behavior).

Delivery is build-to-order. After a short scoping call we confirm the exact models, groups, encryption approach, and integrations, then design, build, and test the module on a staging copy of your database, run UAT with you, and deploy to production with a rollback plan. Typical delivery is one working week from confirmed scope, depending on complexity. Pricing starts from $999 (indicative, single-company base scope); multi-company vault segregation, deeper integrations (SSO/secret-sync, external KMS), stricter compliance and audit requirements, and migrating a large volume of existing credentials increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise.