Security and access
An analyst needs enough access to do the job and no more. A learning database does not model the access controls of a shared production system.
Least privilege
Give a reporting role access to the data it needs, often SELECT on curated reporting objects. Separate reading, changing data and administering the database.
GRANT and REVOKE
Supported engines use GRANT to assign privileges and REVOKE to remove them. Object ownership and inherited roles can affect effective access. SQLite has no comparable server-user GRANT system.
Masking and row restrictions
A masked display can still expose information through other query paths. Row-level policies and view-based access require a threat model and permission tests. Minimize sensitive columns at the source where possible.
Safe inputs and secrets
Use bound parameters for values, allowlist identifiers and keep credentials out of code, screenshots and exports. Read-only access can still disclose sensitive data, so “cannot edit” does not mean harmless.