Skip to content

Release Notes - v16.0

Granular control over schema and table-level access

We are introducing Table Permissions, a new feature that gives administrators more granular control over data access for different user groups.

Administrators can now define which schemas and tables a group can access and assign Read or Write permissions based on the group’s requirements. Specific tables can also be excluded to restrict access to sensitive or restricted data.

  • Schema and table-level access: Configure access to specific schemas or individual tables for each user group.
  • Read permissions: Allow users to view or retrieve data from permitted tables.
  • Write permissions: Allow users to create, update, or modify data on permitted tables, along with Read access.
  • Excluded Tables: Restrict access to specific tables even when broader schema-level permissions have been granted.
  • Group-based permissions: Configure table access once at the group level and apply it consistently to all users in the group.
  • Independent access configuration: Different groups can have different permissions based on their roles and requirements.

Navigate to:

Access Management β†’ Groups β†’ Select a Group β†’ Table Permissions

From the Table Permissions tab, administrators can select the required schemas or tables and assign the appropriate permissions. Use the Excluded Tables section to restrict access to specific tables when required.

With Table Permissions, administrators can:

  • Apply granular access control at the table level.
  • Manage Read and Write access independently.
  • Restrict access to sensitive tables.
  • Simplify access management through group-based configuration.
  • Improve overall data security by limiting unnecessary access to critical data.

We have enhanced Row-Level Security (RLS) to provide administrators with greater flexibility in managing data access across tables, users, groups, and SQL reports.

  • Administrators can now create reusable RLS attributes from Access Management β†’ Row level security.
  • RLS attributes can be assigned to specific users or groups.
  • RLS values can also be added in bulk using the Add from file option.
  • RLS attributes can now be mapped to specific tables and columns.
  • Administrators can search for a table or schema, select the required table, and assign the appropriate column to an RLS attribute.
  • SQL reports now support RLS directly through the SQL query.
  • Administrators can use the rls_filter syntax in the WHERE clause to apply a configured RLS attribute.
  • Support is available for both tables with and without aliases.

Syntax:

Without alias:

{{rls_filter(<tablename>)}}