When not to use it
Table hiding is helpful, but it is the wrong tool for some jobs. Do not let it stand in for real access controls.
Do not rely on hiding when…
The data is regulated or highly sensitive
Protect it at the database (and in Odoo) first; do not depend on STYD hiding alone.
Protect it at the database (and in Odoo) first; do not depend on STYD hiding alone.
You are using shared, high-privilege credentials
Hiding does not fix an over-privileged database account. Use a least-privilege, read-only user.
Hiding does not fix an over-privileged database account. Use a least-privilege, read-only user.
Odoo already governs the access
Use Odoo permissions and record rules; do not replace them with STYD hiding.
Use Odoo permissions and record rules; do not replace them with STYD hiding.
Get the order right
Enforce access at the source, meaning database and Odoo permissions, and treat STYD table hiding as an extra layer on top. Hiding reduces exposure inside STYD; it does not make the underlying data inaccessible, and it only covers the members you hid the table from.