Can I hide or mask specific columns from certain users in iDBQuery?
Yes — iDBQuery supports role-based access control and column-level permissions, so you can restrict or mask sensitive fields like salaries, national IDs, or card numbers for users who shouldn't see them. Combined with row-level security, different people can share a workspace while each only reaches the data they're allowed to.
Not everyone who asks questions should see every field. iDBQuery is architected so access is governed centrally rather than left to trust.
- Column-level permissions. Administrators can restrict which fields a role can query or return, and mask sensitive columns so they're hidden or redacted for users without clearance.
- Row-level security. Alongside column controls, you can limit which rows a user sees — a regional manager to their region, for example — so the same question returns each person's slice.
- Role-based access control. Permissions are assigned by role, making it manageable as teams grow.
Because iDBQuery queries in place and can deploy in your own VPC, on a Desktop app, or fully air-gapped, sensitive data can stay entirely within your walls while these controls decide who reaches what. This is how iDBQuery approaches privacy for PII: leading with architecture and access control rather than any compliance-certification claim. The result is a single workspace the whole organisation can use, where each answer is still cited to source rows, but only within the boundaries each user is permitted to see.
Updated 2026-06-22