Can I give iDBQuery a read-only database user?

iDBQuery is a read-only tool by design: it writes SQL to answer questions and runs it against your data, but it never modifies your database. The safest and recommended way to connect is with a dedicated read-only user.

How to set it up:

• Create a role/user with SELECT-only privileges (no INSERT, UPDATE, DELETE, or DDL).
• Scope it to just the schemas or tables you want iDBQuery to see, if you want to limit exposure further.
• Give iDBQuery those credentials, which it stores encrypted.

With a read-only user, even in the unlikely event of a bad query, there is nothing iDBQuery can change — the database itself enforces the limit. This is least-privilege access at the source, not just a promise in software.

It also pairs naturally with iDBQuery's other safeguards: query-in-place so your data isn't force-copied out, encryption in transit and at rest, role-based access inside iDBQuery, and deployment in your own VPC, on-prem, or air-gapped so data stays in your walls.

Example: a company wants business users to self-serve analytics on the production database without any risk to it. They create a read-only replica user, hand it to iDBQuery, and the whole team gets cited answers — with the database provably protected from any write. You control exactly what that user can see.