Best practices
A few habits keep STYD with Odoo safe, accurate and easy to trust.
Set up safely
Start with read-only, scoped access
With an API key, use a dedicated Odoo user that can read only what STYD needs: Odoo applies that user's rights to every read. With the Bridge, generate the token from a user whose companies are only the ones you want STYD to reach.
With an API key, use a dedicated Odoo user that can read only what STYD needs: Odoo applies that user's rights to every read. With the Bridge, generate the token from a user whose companies are only the ones you want STYD to reach.
Keep Odoo permissions clean
Well-maintained Odoo access rights and record rules are your main control on an API key connection. On the Bridge, record rules are not reproduced, so decide what to share through the token's companies and the mapping.
Well-maintained Odoo access rights and record rules are your main control on an API key connection. On the Bridge, record rules are not reproduced, so decide what to share through the token's companies and the mapping.
Install and sync the Bridge, then map users
Mapping gives each member their own areas and companies. A member who is not mapped gets no Odoo data.
Mapping gives each member their own areas and companies. A member who is not mapped gets no Odoo data.
Tune understanding and verify
Review the AI Guide after connecting
Check how STYD understands your Odoo models and fields, and re-sync after important changes in Odoo.
Check how STYD understands your Odoo models and fields, and re-sync after important changes in Odoo.
Verify multi-company and sensitive data
Check that companies and areas behave as you expect.
Check that companies and areas behave as you expect.
Use it well day to day
- Validate important financial and commercial answers before acting on them.
- Give feedback, and add your own words for Odoo terms in Brief your assistant.
STYD is read-only and does not change Odoo. It explains and recommends. You decide and act.