How to Secure a Flow So It Can't Be Viewed or Copied After Deployment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2025 11:34 PM
We're building a Flow in a scoped app, and we'd like to ensure that when it's deployed to a different instance (such as a customer or client environment), the Flow remains protected. Ideally, we want to prevent even system admins in that instance from accessing or copying the Flow logic.
Has anyone implemented this kind of protection before? Is there a way to make the Flow or its components read-only, hidden, or otherwise secure through scoped app settings or protection mode? Any best practices or suggestions would be appreciated!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2025 11:39 PM
The additional properties of a flow allow you to set protection to 'read only'. At this moment, that's the only protection on it, but that should prevent from copying as well.
I don't think you want to hide it. If anything isn't working, you do want people to check on any errors in the flow, right?
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-25-2025 12:06 AM
Really appreciate the prompt reply!
The problem is with "Read Only " the copy Flow still seems to work.I am trying this on a demo instance.
Do you think that could be the reason?
Also "Read Only" does not seem to protect the Flow from an Admin.Need a Workaround for that.
The idea is to keep the code available only for our team .
