Forum Discussion

SeanMoody's avatar
SeanMoody
Icon for Helper I rankHelper I
1 year ago
Solved

Auto attendant and Call queue historical reports - Version 3.2

So from my understanding of how this report works, it uses OAuth2 authentication which is based off of my credentials. My credentials have been given access to Different AutoAttendant and Calling Qu...
Need Help
SeanMoody's avatar
SeanMoody
Icon for Helper I rankHelper I
1 year ago

Thanks for the explaination.

So if I create a user-to-queue mapping table (for example, email → assigned queue names) then I have 2 additional questions:

1) How do I tie this mapping table into the many tables within this report so it filters the multiple reports ?

 

2) Am I correct in assuming that this table will need to be kept up to date with every change that is made on the teams queue administrative side?

 

Thanks

Sean

Ritaf1983's avatar
Ritaf1983
Icon for Super User rankSuper User
1 year ago

Hi SeanMoody 

Regarding the RLS mapping table:
This is a table that needs to be connected to your data models.
The model itself should be structured accordingly — for example, there should be an Employees table that is linked to the Sales table through some key.
I'm attaching a link to a tutorial video about RLS.
I believe it will help clarify things for you

https://www.youtube.com/watch?v=jphj40tBPD8&t=3s

If this post helps, then please consider Accepting it as the solution to help the other members find it more quickly

  • SeanMoody's avatar
    SeanMoody
    Icon for Helper I rankHelper I
    1 year ago

    Thank you for your advice Rita I will look at the video on Row level Security.
    Sean.