Read-only database users

STYD only needs to read your data to answer questions. Connecting with a read-only database user is the safest way to set up a connection.

Why read-only matters

A read-only user follows the principle of least privilege: it can give STYD exactly what it needs (the ability to read) and nothing more. Even though STYD is designed to run read-only queries, a read-only user is an extra, independent safeguard at the database level.

What a read-only user should allow

  • permission to connect to the database
  • read (SELECT) access to the tables and views you want STYD to use

What it should not allow

Avoid granting write or structural permissions: no INSERT, UPDATE, or DELETE; no DROP, ALTER, or CREATE; and no administrative or superuser privileges.

For production systems

On a production database, ask your database administrator to create the read-only user and grant access only to the tables STYD should see. This keeps access scoped and auditable.

For Odoo, prefer the Odoo permission model and the Odoo Bridge security setup — see the Odoo section. Database-level read-only access is still a sensible baseline.