What admin controls does iDBQuery give an account owner?
An iDBQuery account owner gets centralised admin controls for users, roles, and access: adding or removing people, assigning roles and permissions, managing connected data sources, configuring SSO and session policies, and reviewing audit logs. This puts governance of who can see and do what in one place.
The account owner and admins hold the levers that govern an iDBQuery workspace.
- User management - invite, remove, and organise users, or automate it entirely through SSO and SCIM from your identity provider.
- Roles and permissions - assign role-based access, and apply row-level, column-level, and masking rules so people only reach the data they should.
- Source governance - control which data sources are connected and who can query them.
- Security policy - configure SSO, session timeouts, MFA through your IdP, and IP allow-listing.
- Oversight - review audit logs of who did what and export them to your own tooling.
For example, an admin onboarding a new department can create a role, grant it the two relevant projects, mask salary fields, and hand access to the whole team through an SSO group in minutes - then see every action in the audit log. These controls exist so governance scales as more people self-serve their own answers, which is the whole promise of letting non-technical staff query data safely. They sit on top of iDBQuery's architecture: query-in-place so data is not copied out, and encryption in transit and at rest. Strong central administration is what makes broad, safe access possible. Contact us for an admin walkthrough tailored to your organisation.
Updated 2026-06-22