Does iDBQuery support column-level permissions?
Yes. iDBQuery supports column-level permissions so specific fields, such as salary, national ID, or card numbers, can be hidden from users who should not see them, even while they query the same table. This works alongside role-based and row-level controls so people only reach the columns their role allows.
Column-level permissions let you restrict access to individual fields rather than whole tables, which is essential when a table mixes sensitive and non-sensitive data.
- Hide sensitive columns - a support analyst can query the customers table for order history while columns like national ID or full card number stay out of reach.
- Role-scoped - permissions attach to roles, so finance may see compensation fields while a broader team sees only headcount and department.
- Layered controls - column-level rules combine with row-level security and RBAC, so both which rows and which columns are governed per user.
For example, an HR generalist and a payroll manager can both ask about staffing, but only the payroll manager's answers include salary figures - the generalist's queries simply exclude that column. Because iDBQuery writes the SQL and cites each figure back to its exact source row, these limits are applied where the query runs, and the citations never expose a field the user is not permitted to see. This ties into iDBQuery's wider design: query-in-place so data is not bulk-copied, encryption in transit and at rest, and permissions enforced consistently across every connected source. It is a practical way to give more people self-serve access without over-exposing sensitive fields. Contact us to map column permissions to your roles.
Updated 2026-06-22