Bknd Row-Level Security FAQs

Question 1

What is the difference between RLS and standard permissions in Bknd?

Accepted Answer

Standard permissions control access to entire entities (e.g., 'Can this user read posts?'), while RLS uses filter policies to control access to specific rows within an entity (e.g., 'Can this user read *only their own* posts?').

Question 2

Can I configure RLS through the Bknd Admin Panel UI?

Accepted Answer

The Admin Panel UI is read-only for RLS policies. To implement or modify row-level security, you must use code mode within your Bknd configuration file.

Question 3

Does Bknd support complex RLS conditions like 'Public OR Mine'?

Accepted Answer

Yes, Bknd filter policies support MongoDB-style operators like $or, allowing you to create rules where a user can see records if they are marked as public OR if the user_id matches their own.

Question 4

Can I allow admins to bypass row-level security filters?

Accepted Answer

Yes, by setting 'implicit_allow: true' on an admin role, you can bypass filters, allowing that role to see all records regardless of ownership fields.

Question 5

How do I ensure the owner ID is correctly set when a new record is created?

Accepted Answer

The recommended approach is using a Server Hook with the DataRecordMutatingEvent. This allows the server to automatically inject the authenticated user's ID into the record, preventing clients from spoofing ownership.

Bknd Row-Level Security

About

Key Features

Use Cases

Bknd Row-Level Security

About

Key Features

Use Cases