Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Vote for your favorite vizzies from the Power BI Dataviz World Championship submissions. Vote now!
Hi ,
I'm working with Power BI Desktop, and I have a project with 10 pages. I also have a navigation menu for all the pages. Each page is related to a specific site, and I have 10 channels in Microsoft Teams, one for each site. Now, I need to share each page in its corresponding Teams channel .
Solved! Go to Solution.
@Yakout , This page RLS solution is something coming to me first, see if that can help
https://www.youtube.com/watch?v=FrEDZZXiit8
Hi @Yakout ,
Thanks for reaching out to the Microsoft fabric community forum.
@amitchandak made a good point on RLS, I think for your use case that is the best possible option, use Row Level Security (RLS) to ensure each Teams channel only sees its corresponding report page. In this setup, you define RLS rules so each user or group in a Teams channel is automatically restricted to data for their specific site. You can then apply page-level logic such as conditional navigation, measure-driven visibility, or calculation-group-based page switching to ensure the report shows only the relevant page for that site and hides or disables access to all others. With this configuration, you embed the same report in all 10 Teams channels, and the RLS rules ensure that each channel’s members are automatically directed to the correct page and cannot access content intended for other sites. This method offers strong security and minimizes maintenance because you manage one report instead of ten, though it does require more advanced setup and testing to ensure the navigation and page-visibility logic behaves as expected.
I hope this information helps. Please do let us know if you have any further queries.
Thank you
Hi @Yakout
May I check if this issue has been resolved? If not, Please feel free to contact us if you have any further questions.
Thank you
Hi @Yakout
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank you.
Hi @Yakout ,
Thanks for reaching out to the Microsoft fabric community forum.
@amitchandak made a good point on RLS, I think for your use case that is the best possible option, use Row Level Security (RLS) to ensure each Teams channel only sees its corresponding report page. In this setup, you define RLS rules so each user or group in a Teams channel is automatically restricted to data for their specific site. You can then apply page-level logic such as conditional navigation, measure-driven visibility, or calculation-group-based page switching to ensure the report shows only the relevant page for that site and hides or disables access to all others. With this configuration, you embed the same report in all 10 Teams channels, and the RLS rules ensure that each channel’s members are automatically directed to the correct page and cannot access content intended for other sites. This method offers strong security and minimizes maintenance because you manage one report instead of ten, though it does require more advanced setup and testing to ensure the navigation and page-visibility logic behaves as expected.
I hope this information helps. Please do let us know if you have any further queries.
Thank you
@Yakout , This page RLS solution is something coming to me first, see if that can help
Vote for your favorite vizzies from the Power BI World Championship submissions!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
Check out the January 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 57 | |
| 52 | |
| 45 | |
| 17 | |
| 16 |
| User | Count |
|---|---|
| 109 | |
| 108 | |
| 40 | |
| 33 | |
| 26 |