Does iDBQuery have role-based access control and permissions?
Yes. iDBQuery uses role-based access control so administrators decide which sources, workspaces and capabilities each person can use, and sensitive operations are limited to the roles you authorise. Permissions are enforced on every query, not just at the screen level, so people only ever see the data their role allows.
Role-based access control (RBAC) in iDBQuery means access is granted by role rather than person by person, which keeps permissions manageable as teams grow.
- Administrators manage the workspace, connect and configure data sources, and set who can do what.
- Members ask questions, build reports and dashboards, and see cited answers — but only across the sources their role is allowed to reach.
- Sensitive capabilities such as connecting new sources or running operational actions are gated to authorised roles, so an ordinary user cannot quietly expand their own reach.
Crucially, permissions are enforced at the data layer — when iDBQuery writes and runs a query, it does so within the boundaries of the requesting user's role, so restrictions can't be bypassed by rewording a question. This pairs naturally with SSO: your identity provider proves who someone is, and iDBQuery's roles decide what they may touch.
For regulated or multi-team environments, RBAC lets you separate, say, a finance workspace from an operations workspace so each group only works with its own sources. Combined with iDBQuery's deploy-anywhere architecture — cloud, private VPC, Desktop or fully air-gapped — you can keep both the data and the permissions entirely inside your own walls. Every access is captured in the audit log so you can review exactly who could see what.
Updated 2026-06-22