Best practices
Security in STYD comes from a few good habits layered together. None is absolute on its own, but together they keep your data well protected.
Access and credentials
Connect with read-only database credentials.
Use least privilege: grant access only to the data STYD needs.
Do not share API keys; revoke ones you no longer use.
Remove members who no longer need access, and give viewer or member roles by default.
Configuration and data
Review the AI Guide and table visibility, especially for sensitive tables. Visibility is set for each member, so check it when a member joins.
Validate Odoo permissions and record rules where Odoo is connected.
Review the flags on columns that look like personal data regularly.
Read What leaves STYD and the Privacy Policy before you connect sensitive data.
Test risky changes in a staging environment where possible.
Day to day
- Confirm you are in the right workspace before asking questions.
- Validate important answers before acting on them.
- Report wrong or unsafe answers through the feedback buttons.
No setup is perfectly secure. Keep these layers in place, review them periodically, and enforce real access controls at the database and in Odoo.