Hi @jaryszek ,
Thank you for reaching out on the Microsoft Fabric Community Forum.
It's a system-generated hash that reflects the current state of security bindings (like RLS, access control) in your Power BI or Microsoft Fabric project. Stored in localSettings.json, it tracks security-related metadata.
Even without explicit security setup, Power BI/Fabric tools generate default security structures on save/publish.
Minor internal metadata changes (GUIDs, timestamps, etc.) can regenerate the signature.
So it can change even if you didn’t touch security settings.
Is it controlling anything?
Only if you have security bindings set up (like row-level security, workspace-level access rules, etc.).
If you don’t, the securityBindingsSignature is basically idle — just a fingerprint of “current empty/default state.”
So no, it doesn't restrict access or apply security by itself. It just tells the system: "Here's what the security config looked like at this save point."
when does it regenerate?
Saving a report.
Editing the .bpip file.
Changing anything that touches:
Access Control settings
Dataset bindings
RLS definitions
Linked workspace items
If this response is helpful, please consider marking it as the accepted solution and giving it a thumbs-up to help others in the community.
Thank you!
