This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
We currently have about 20 reports planned for our first Power BI project.
Managing these all in one pbix file is manageable, however, some of our other projects could see dozens of datasets and hundreds of reports.
Wondering what you guys have done from the point of management for larger datasets (or ones that are growing)?
I know we can split the dataset/report into two files (linking the dataset file to the report file) to split the logic/viz.
While that's useful to some degree, our challenge is mostly related to RLS.
How would we ensure proper access via RLS with the entire dataset when our RLS has so many conditions.
For RLS:
Trying to reuse the RLS above and ensure filters are properly handled for all reports is especially challenging.
Keep in mind this doesn't cover all our RLS conditions, and some of them may be stacked (e.g. user works for company X and is in office Y).
We're working with an archaic system, so there isn't opportunity for us to improve the db structure.
Just trying to find a way to work with it to pull improved analytics.
The idea here would be use have one project that handles RLS + filters for our web app to tie into.
Then reuse that RLS dataset for other datasets to ensure proper access is granted to the user and perform appropriate calculations based on their access.
Solved! Go to Solution.
Hey @ctoscher ,
yes, you can add them manually, one by one in every workspace and then map the role - one - by - one.
And don't forget to manually remove them everywhere when they change department or go out of your company...
To be honest, I would not go that way, that's not really manageable if you're more than 5 people in your company.
Another approach is you can script that and use the Power BI REST API:
Groups - Add Group User (Power BI Power BI REST APIs) | Microsoft Docs
Best regards
Denis
Hey @ctoscher ,
dozens of data sets and hundreds of reports are common. Usually you split them by department or project, that you have a few workspaces with a few data sets and reports each. That is managable then.
You can create different roles for each data set.
The roles you would assign by AD groups to make it more manageable. A user can also have multiple roles as he might be responsible for multiple countries or something similar, then the access is adding up.
Thank you @selimovd.
Is there any way to manage users without AD?
We have AD, but as mentioned, it's legacy software, so we're quite limited in its capacity and must tie into SQL.
Hey @ctoscher ,
yes, you can add them manually, one by one in every workspace and then map the role - one - by - one.
And don't forget to manually remove them everywhere when they change department or go out of your company...
To be honest, I would not go that way, that's not really manageable if you're more than 5 people in your company.
Another approach is you can script that and use the Power BI REST API:
Groups - Add Group User (Power BI Power BI REST APIs) | Microsoft Docs
Best regards
Denis
Hey @ctoscher ,
did it work with the scripting via REST API or the AD groups?
I'm curious if you could solve this issue 🙂
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 34 | |
| 31 | |
| 30 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 63 | |
| 53 | |
| 31 | |
| 23 | |
| 23 |