Hey, @Sid_Takali - While that CSS will work there, that is the only place it will work. I believe the author will still show up in searches (potentially) and OOTB widgets such as Most Viewed, Featured, etc. To remove the author in all locations, you either control the system property, or, you would have to Clone all OOTB widgets (ones I mentioned above), and change the server script as well as the CSS.
I have done just the CSS before and it did not remove from all locations as per requirements (typical if multiple groups are involved, all groups would want to remove the author. I have found through customers that end users will often see the name of the author to an article, and start reaching out to them directly. Something that is usually not wanted by an organization). Here, I have done just as you have shown, and here is the main page with the widgets and the article view itself (typically the widgets are being used which is why I wanted to show them there):
From Search:
So yes, adding changes to the CSS and server script will work, you then have to take into account cloning those widgets, as they are protected by Read-Only policy from ServiceNow. Those would then become the customers responsibility with future upgrades.
Collectively, best to decided which is the best route. Are all departments involved in the instance okay with removing the author, or, is just HR for example? Control the system property, or, clone multiple widgets to change CSS and server script (keeping in mind, now you own those widgets and they will not receive any future updates pushed out by SN)?
Either way you go, you have options @SNhydrone - to remove author from view which is nice. But you should consider all aspects. If other departments are involved and do not want to remove author, then you should not use the system property as I have mentioned.
Hope this helps!
Cheers,
-Rob
Hi! I've used below
.author {
display: none;
}Below are the SS:
Below "Revised by [Author Name]" is still displayed below including in Most useful part
