Odoo connection
STYD connects to Odoo in one of two ways: with an Odoo API key (the quickest way, with one shared Odoo identity) or through the STYD Bridge (a free module you install in Odoo, with a rights check for each member). A direct read-only database connection stays available for setups where neither can be used.
API key or Bridge?
Both are read-only. The difference is whose Odoo access is used.
Works with Odoo 15 to 20, on Odoo Online, Odoo.sh and on-premise. Enter your Odoo address first: STYD detects the version, then asks only for what it needs. That is the API key on Odoo 19 and later, plus the Odoo login and the database name on Odoo 15 to 18 (“Find my database” can fill it in). Create the key in Odoo: your user menu, My Profile, Account Security, New API Key (on Odoo 15 and 16, turn on developer mode first, then Preferences, Account Security). Odoo itself applies that user's rights and record rules to every read. Everyone in the workspace sees what that one Odoo user sees: there is no member mapping.
Best for trying STYD and for small teams.
Install the module in Odoo and connect it with your Odoo base URL and a bridge token. Each workspace member is mapped to their own Odoo user, and STYD limits that member to the areas their Odoo groups give (Accounting, Sales, Purchase, Inventory) and to their companies. Odoo's record rules are not reproduced (see Record rules). Odoo 15 to 19, on Odoo.sh or on-premise (not Odoo Online). See Security for what this does and does not enforce.
Best when IT needs control for each member.
How STYD connects
Your Odoo URL (the public HTTPS address you open Odoo with) and the API key. On Odoo 15 to 18, also the Odoo login and the database name (both required; on Odoo Online the database name is usually the first part of your address). On Odoo 19 and later, the database name only when your server hosts several Odoo databases. The key is stored encrypted and never shown again. If Odoo blocks external access on your plan, we’ll tell you clearly. On some Odoo Online plans, Odoo limits API access.
Your Odoo base URL (a public HTTPS address; plain http and private or local network addresses are refused) and a bridge token generated in the module. STYD never needs your database credentials.
A read-only PostgreSQL connection to the Odoo database (host, port, database, user, password), for environments where neither an API key nor the module can be used. STYD then reads with the database user's permissions, without any Odoo user for each member, and its Odoo skills are narrower (for example, no stock, purchase orders or vendor bills).
Where it is managed
Odoo connections are added under Settings → Connections with Add Odoo connection, then choosing API key or Bridge. Each connection's card shows its sync status, rights and companies, and AI Guide, with Re-sync (it also rebuilds the AI Guide) and Archive. For a Bridge connection, members are mapped to their Odoo users under Settings → Members → Odoo access. The number of Odoo connections does not depend on the plan. A workspace can hold up to 50 active connections of all kinds, as a safety limit, and the free access covers one Odoo connection and one database.
Read-only and safe
If your Odoo is behind a firewall
If your site sits behind a firewall such as Cloudflare, it can block STYD’s server before the request reaches Odoo. STYD then tells you that your site’s firewall blocked it: “Your server is blocking STYD. If it is behind Cloudflare or a firewall, allow STYD’s IP addresses.” The fix is to allow these two addresses, which STYD uses to reach your Odoo:
109.123.235.222(IPv4)2407:3640:2324:5796::1(IPv6)
In Cloudflare:
Another firewall or hosting provider works the same way: add both addresses to its allow list.