Row Level Security

[NimaiAhluwalia]

Imagine this scenario.

2 user groups.  A & B which are aligned to sales channels A and B.

Each channel contains customers.  Lets say A1, A2, A3 and B1, B2 B3

Users in group A need to see all sales in channel A and be able to see the detail of sales for A1, A2 and A3.  They also need to see an aggregated view of sales for Channel B, but NOT the detail.  So all of B aggregated together.

Same is true of users in group B.  Then need to see all of B sales and B1,B2, B3 but only an aggregated view of sales for A.

RLS no good as that would prevent A from seeing any of B and vice versa.

What is the solution??

@amitchandak

[amitchandak · Accepted solution]

@NimaiAhluwalia , I would advise creating a table having only group-level data, not having customer data, and joining. That will allow you to see that data.

Other way would have a column and access in RLS table, joining back to Customer, filter from RLS table to Customer. So new column(Customer Share Group) in RLS will be used in visual also

Customer , Customer Share Group, Email

A1 - A1 - a@email.com

A2 - A2 - a@email.com

A3 - A3 - a@email.com

B1 - B - a@email.com

B2 - B - a@email.com

B3 - B - a@email.com

A1 - A - b@email.com

A2 - A - b@email.com

A3 - A - b@email.com

B1 - B1 - b@email.com

B2 - B2 - b@email.com

B3 - B3 - b@email.com

This can be intermeditae table if you want to avoid too much of data in RLS