Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hello out there! I'm wondering what people have done to attach (internal) documentation to a workspace that's been shared with users.
The hack I will jokingly suggest is to create a pbix called "Don't README" and put RLS on it, but don't put any of the users on a role. So if they click on it, they don't see the data. And this is where I'd put my notes.
I'm only half-joking, since this might be what I end up doing. And if the workspace is accessed via an app, I can block this report from the app. Is that the best approach? Any other ideas?
Thanks,
Amon
Solved! Go to Solution.
In workspace settings there's a description field, I often find this sufficient. Sometimes I create auditing report pages that I use for troubleshooting, I hide them so they only show in Power BI Desktop. Your idea of creating a separate report also has merit, I'd call it "Documentation" and only put the workspace admin(s) on an RLS role, if end users shouldn't see any of that documentation.
In workspace settings there's a description field, I often find this sufficient. Sometimes I create auditing report pages that I use for troubleshooting, I hide them so they only show in Power BI Desktop. Your idea of creating a separate report also has merit, I'd call it "Documentation" and only put the workspace admin(s) on an RLS role, if end users shouldn't see any of that documentation.
Thanks @otravers . I do use the description field for things that the users ought to see, and hidden report pages for notes specific to those items. I'm glad you think my joke has merit! I wonder if anyone else has any other ideas?