Could you elaborate a little on the content? Is all of this feeding from a single datasource or a single workbook?
It's a single data source but multiple workbooks.
My understanding is that the row level is easy to achieve with a security table that I join. The challenge (?) is to give permissions to the aggregations, so that a single sales person can see the total sums, average numbers per sales person etc.
I wonder if that is possible to do in a single data source?
Clear as mud...?
1 of 1 people found this helpful
Great that's easier to design a security model. Indeed row level security using a join to marry up your user base against your data will be the automatic way.
The tricky part comes for the top level aggregations (by region, store and country) you could create rows of data for these aggregations and make those available for the corresponding user base. An alternative could be to create those aggregations as separate data sources for individual worksheets within a dashboard, and manage permissions for those at "view level". The latter will on only work with projects that are not "locked" so permissions are not inherited from the project but individually set.
Let me know if this helps or you need more clarification.
Sorry for taking so long.
I think I get the concept.