Conflict between BlockAddImageByUrl and BlockStockAndWeb

27 views
Skip to first unread message

Kate Masterson (Staff)

unread,
Mar 10, 2026, 2:51:14 PM (4 days ago) Mar 10
to xFanatical Safe Doc Community
We have the following two settings in our instance:

"BlockStockAndWeb": {
        "Value": false
     },
"BlockAddImageByUrl": {
        "Value": true
    },

With BlockAddImageByUrl set to true, the "By URL" option is removed from the Insert > Image menu, which is what we want. But it also appears to prevent anything from loading in the Insert > Image > Stock & Web. Students see the Stock & Web menu option, select it, and the side menu pops out. But no images load in the side menu. Is this an intended behavior?

Thank you for any insight you can provide!
Kate

Kate Masterson
Assistant Director of Digital Security & Privacy
Carmel Clay Schools
Carmel, Indiana
Screenshot of Untitled presentation - Google Slides.jpg

Jason Huang

unread,
Mar 10, 2026, 5:13:01 PM (4 days ago) Mar 10
to xFanatical Safe Doc Community, kmas...@ccs.k12.in.us
Hello Kate, 
It is not the intended behavior. When the BlockStockAndWeb policy is turned off, at least the Stock images ➔ section should still appear so that students can find stock images.
Since the Stock images ➔ section is not showing, it's unclear whether factors than xFanatical Safe Doc may be affecting the functionality. Our team would be happy to help identify the root cause.
screenshot_2026-03-10_13-53-14.png

The 2 policies BlockAddImageByUrl and BlockStockAndWeb do not conflict. In the Stock & web feature, 2 separate policies manage the subtle features.
If you need these features, you can turn off both policies. 
"BlockGIFAndSticker": {
  "Value": false
},
"EnableImageSearch": {
  "Value": true

I hope it works for you. 
Thank you.
--
Jason Huang
Product Manager at xFanatical

Matthew Weiner

unread,
Mar 11, 2026, 9:55:32 AM (3 days ago) Mar 11
to xFanatical Safe Doc Community
Just as a heads up I am seeing the exact same behavior on my end, the teachers just started reporting it this week, this may be an unintended consequence of a code change by Google.  I'd be willing to work on finding a root cause if necessary.
Reply all
Reply to author
Forward
0 new messages