Static HTML Content Block for all roles

Lisa Baremore · ‎12-26-2017

Hello!

Is there a way I can open up the use of the Static HTML Content Block for users with certain roles or all users with the itil role? Is there a property I can set for this somewhere? Now that we upgraded to Jakarta and all users can create and use dashboards, we are getting a lot of requests for this type of functionality.

Thanks!

Lisa Baremore · ‎01-09-2019

So actually, I needed to add ACLs for create, read and write in order to implement this where I work today.

Objective: Provide the ability for users with certain roles to create and update New Static HTML content blocks without giving them the role content_admin. In my use case, I am providing this to the roles report_creator and pa_power_user.

Solution: Add Create, Read and Write ACLs that include all 3 roles on the table content_block_static

All of these ACLs contain all 3 roles (report_creator, pa_power_user, content_admin)

View solution in original post

Michael Fry1 · ‎12-26-2017

Looking at the read-ACLs, limited to a role content_admin:

So I'd try adding a new read-ACL with ITIL role and see if that works.

Lisa Baremore · ‎12-26-2017

I will try this! Thank you so much!

Dan Hinrichs · ‎11-14-2018

Hi Lisa, I've received a similar request. Did you end up rolling out use of the static HTML content block for itil users? If so, how has the experience been? Has it created a bunch of extra admin work to clean up content blocks? Any negative platform impact?

On the surface this seems innocent enough to open up, but if it was truly that innocent I wouldn't have expected this to be limited to content_admin and admin OOB.

Thanks so much!

Lisa Baremore · ‎01-09-2019

Hi there @dhinrichs, So sorry to be responding so late!

In the company I worked at before (Verizon) I did open that up to all itil users and it wasn't so bad. A select group of reporting users really liked this functionality and used it efficiently. However I never introduced any monitoring or governance around it so as you say, it could get out of hand with many abandoned records no longer on dashboards.

There was not any impact to platform performance other than the normal things that impact dashboard load time. One of those things involves the number of widgets on a dashboard tab. Every content block you add is another widget so even excessive amounts of these could add up, so a best practice was to have as few as possible, combining info into a few as needed.

Where I work today (Walmart) I had to implement it a little different. Instead of opening it up to all roles, I needed to open it up to select roles. Walmart has an incredibly larger user base than Verizon so I do need to employ some governance and cleanup around it to keep things manageable.

Implementation is what I am working on today. After that I am going to create a way to find out where the content blocks are being used on a dashboard or UI page so I can create a cleanup process. I don't see an OOTB way to do this today so it will require a view or table. I don't have the answer yet, but it's next on my list. Once I create it, I will share it here.

Thanks!