13. Odoo connection

Admin only

How togrant.com talks to your Odoo. Configured per tenant.

Fields

  • URL — your Odoo base URL (https://your-org.odoo.com).
  • Database — Odoo database name.
  • Username — service account email.
  • API key — Odoo "Developer mode → API Keys → Create" output. Stored AES-GCM-wrapped in D1; never shown back in plaintext.

Test connection

The "Test connection" button does a live db.list + common.version round-trip and shows the response inline. Use this after every credential change.

Standard Odoo API only. togrant.com does not require a custom Odoo module, Studio fields, or server actions. The three analytic plans (Project / Donor budget line / Donor budget detail) are created on demand by the sync; nothing in Odoo needs hand-tuning beyond installing the standard Accounting + Analytic Accounting apps.

Project ↔ Odoo sync is decoupled from budget sync

Linking a project to an Odoo project record and pushing its budget are two separate steps. This matters when staff need to book hours or expenses against the Odoo project before the donor has signed:

  • Application phase (pre-award) — from the application's Projects card you can Connect to Odoo per draft project and link an existing Odoo project id. No budget syncs at this stage; the Plan 2/Plan 3 accounts only get created after award.
  • Award — the linked Odoo project id carries through automatically to the materialised real project. Plan 2 (donor budget line) accounts and Plan 3 (detail) accounts are then created and the budget syncs in one go.
  • Post-award reallocations — every detail edit pushes an incremental Plan 3 update; no full re-sync needed.
Related