New feature of comments in Reports is really nice and of great value. Sometimes though comments should not be visible to anyone with access in report. It might me a good idea to create an option box for sharing comments only with account tagged.
3 Comments
- bola_labulo3New MemberI agree with this, I'm sure many have had to disable this feature as there is no way to control who can see what. I'm having to integrate power apps at the moment to have a commenting system that respects security settings however this means users don't benefit from handy features like automatic bookmarking. If RLS is too difficult to implement at this level (I understand why) then having the ability to lock visibility to the poster of the comment and whomever they have tagged with an @ is the next best thing. This shouldn't affect what the owner of the report and those given full access can see however. I think this should be prioritised if it's a viable feature as security was one of the most mentioned issues with commenting even back when it was first introduced for dashboards. At report level it is even more important to have some level of control over who can see what.
- John_AtkinsonNew MemberAgreed! This has come up during our training sessions for two apps - one of which is used by 1100 users....you can imagine the mess of 'Comments' that will accumulate there and potential embarrassments if there are no options to control who sees what.
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Allow NotebookUtils getSecret() to authenticate with Workspace Identity
Current behavior In Microsoft Fabric, notebookutils.credentials.getSecret() authenticates against Azure Key Vault using the identity of the user who executes the notebook. This behavior appli...tmihara24 minutes agoNew MemberNew15Views1like1CommentAllow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels7 hours agoAdvocate IIINew184Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen8 hours agoAdvocate INew296Views47likes2Comments