Static HTML Content Block Added- Users See Broken Links

[jlaps]

I created a few static HTML content blocks to hold images for headers. This looks perfect when I look at it, but when an ITIL user tries, they get broken image links for the content blocks.

Do we really need to add ACL rules so people can see images we specifically add to content blocks? Please tell me I am missing the easy mode.

[Claude DAmico · Accepted solution]

I've run into something like this before, but in knowledge articles with knowledge blocks. We had transitioned from a customized solution similar to knowledge blocks which we needed way before the OOB method was available. After the transition, there were still some blocks that were referencing sys_attachment records that are images on the customized records which we removed access to causing the links to appear broken for those who did not have access. However, image references to db_image records were not impacted.

This could be one of those cases where the images are sys_attachment instead of db_image in which case an ACL may need to be reviewed. That is not likely the case with db_image.

What's your case? Where are these images stored?

[jlaps]

Thank you for your feedback. This got me to look at how I created these, which was just pasting the image into the block as I was creating it. This had them as ATTACHMENTS with all that entails. I removed the image I pasted in, and added one from the library, and ITIL users can see them fine. 

Thanks for the tip!

[Adam43]

Claude- I took the db_image suggestion and used it to resolve similar case for Guided Tours where sys_attachment did not work.  db_image worked for my GT creator, but he does not have access to db_image to add new records to it.  only admins do- it turns into another ACL issue just on another table.  Any thoughts?

[Claude DAmico]

If a user needs access to a table to complete work, you're pretty much limited to adjusting user roles and/or ACLs.