Row-Level Security (RLS) with an Excel User Mapping

Q&A
,
1

Hello,

Regarding Row-Level Security (RLS), can access be managed using an Excel file that contains two columns: User and Production Line (Band)?

The idea is to maintain an authorization matrix in Excel, where each row defines which production line(s) a user is allowed to access. For example:

  • User A → Production Line A
  • User B → Production Line B

Based on this mapping, users would only be able to view data for their authorized production lines. If they select a production line outside their assigned permissions, the dashboard would display “No Data.”

Is this approach supported and recommended? Thanks!

2

Hi @01267ts

Yes, this approach is fully supported and recommended. It is exactly how Row-Level Security is designed to work in Quick Suite Enterprise Edition.

You create a permissions dataset (your Excel file) and attach it to your main dataset. Quick Suite then automatically filters rows for each user based on the mapping you define.

Your Excel structure would look like this:

UserName ProductionLine
user_a@company.com Line A
user_b@company.com Line B
user_c@company.com Line A
user_c@company.com Line C

Key Points:

  • UserName column must match the Quick Suite username exactly (typically the email address or SSO identity). You can also use GroupName for group-based access.

  • Field names must match the column name for your restriction field (e.g., ProductionLine) must match the corresponding column name in your main dataset exactly. All field names and values are case-sensitive.

  • Multiple production lines per user, if a user needs access to more than one production line, simply add one row per line (as shown for user_c above).

  • Users not listed by default, any user without an entry in the permissions dataset will see no data. This gives you the No Data behavior you described when a user attempts to access a production line outside their authorization.

Official Documentation: