I have a scenario where employees have access to their own leave records (sickness, annual leave etc.) as well as the HR Team and their Manager. These leave records feed into a Rota which all users have access to.
Is it possible to restrict access so employees cannot access other employees leave records directly but the details say date range of leave and type of leave are passed through to the rota and used to filter out users who are not available? Possibly not the best explanation but its a case of not being able to view/edit other employees data but being able to use said data in formulas/filters elsewhere
Short answer, yes it’s possible, but how depends on a lot of things.
There are a lot of ways to hide or prevent certain screens and components from be accessible by other users by using filters, visibility conditions, conditions in custom actions, etc. All depends how how your app is set up and how users are gaining access to other user’s data.
There’s also the factor of securing data. You can hide it by using the above methods, but that data would still be downloaded to all user devices and someone technical enough could find it. Hard to say if that’s important to you or not. Row Owners would be a simple solution and truly secure the data, but makes the rota difficult if all leave data is not accessible to all users.
To help provide an adequate solution, we would need to know more about how your data and screens are set up and how users are currently accessing other users data.
2 Likes
thanks @Jeff_Hager this what I thought. If the data is visible via web inspector on the browser it’s not secure. Out of interest does Big Tables treat filters/visibility conditions differently in that the data isn’t downloaded? I got the impression that Big Tables was more server centric?
I think you may be correct that Big Tables are more server centric. I believe Big Tables will retrieve only the data it needs. I’d have to divert to @Darren_Murphy though as he may know for sure the ins-and-outs of how it works. I’ve never used Big Tables.