Saved searches should only be restricted to the users who created them or limited to their accessible stream
Agreed: But it should be configurable.
+1
+1 - Users with read-only roles can edit and delete all saved searches across the system, and not just their own, which is a bit alarming. It would be great if it were configurable whether a given role can add, edit, delete, or view\use a saved search within various scopes (streams, inputs, etc.), and whether those saved searches are only visible to them or if they're global saved searches that any user can view\use.
+1
You guys have done a great job putting in top of the line enterprise permissions and access management. This is probably one of the last security holes stopping me from getting more traction getting this system officially adopted in my organization.
+1
+1
+1
+1
+1
Any update on this issue?
+1
wow 5 years for a feature request?!
+5
+1
Most helpful comment
+1 - Users with read-only roles can edit and delete all saved searches across the system, and not just their own, which is a bit alarming. It would be great if it were configurable whether a given role can add, edit, delete, or view\use a saved search within various scopes (streams, inputs, etc.), and whether those saved searches are only visible to them or if they're global saved searches that any user can view\use.