What is the minumum role required to access content library as part of Employee Center Pro

Mahesh Kumar2
Tera Expert

Hi Guys,

 

We are trying to implementing News Center via EC Pro. But we are lack of information about, what is the minimum role required to create News Articles through content library which we can give to end users. Please help with it.

 

Apart from this, I have a doubt related to Content approval process. We can add approvals thorough back end via schedule content records but same provision is not available in content editor while creating publish plan. Is there any specific reason to not implement approvals in content editor.

5 REPLIES 5

bubuprasadswain
Tera Guru

People with content admin can create content from content library.

bubuprasadswain_0-1712746949954.png

 

For Approvals, I have also noticed the same Approvals are not directly configurable from editor.
But have you considered Content Governance process. 

Deepak Shaerma
Kilo Sage

Hi @Mahesh Kumar2 
When it comes to permissions and roles for creating News Articles through the content library, understanding the minimum required role is crucial for streamlining the process without compromising security and governance.  However, common roles that might have the necessary permissions:
content_admin: A role typically reserved for content administrators who have comprehensive control over the content, including creating, editing, and managing content articles and news. This role might be more permissive than you’d want for an end user primarily focused on generating content.
content_author: This is likely the minimum role required for end users to create and manage their articles in the Content Library. Users with this role can usually create new content items and edit their own.

The reason approvals might not be readily available or directly implemented in the content editor could be due to:

1. Simplicity and User Experience: Keeping the content publishing interface simple for authors can help reduce confusion and streamline the content creation process.
2. Approval Workflows Complexity: Approval processes can vary greatly between organizations and even between different types of content within the same organization. Incorporating this directly into a publishing plan via the editor could necessitate a generic one-size-fits-all approach that might not suit all needs.
3. Security and Governance: Managing approvals through a backend process allows for a more controlled environment, where specific roles can oversee and manage the approval process separately from content creation.

Note: To achieve a smooth implementation, consider creating custom roles if existing ones don’t perfectly fit your needs for creating news articles.
Note: Please Mark this Helpful and Accepted Solution. If this Helps you to understand. This will help both the community and me..
- Keep Learning ‌‌
Thanks & Regards 
Deepak Sharma

Thanks Deepak for this in depth explanation. I just have one doubt here. My instance does not have content_author role. So should we create one? 

I cross checked some ACLs and and observed an ACL sn_cd_content_news.* for Create operation on content manager role. Is this role fine or should we create the content_author separately. If yes, What ACLs we should create for the content_author role.

Pooja_Patil
ServiceNow Employee
ServiceNow Employee

@Mahesh Kumar2 , Content Publishing ships sn_cd.content_admin and sn_cd.content_manager out of the box. Please give sn_cd.content_manager role to the users who will create and manage contents. With sn_cd.content_admin you get additional access to some other additional modules and create templates, categories for news, create video providers

You do not need to create any roles or update ACLs.

For approval process please refer - https://docs.servicenow.com/bundle/washingtondc-employee-service-management/page/product/employee-ce...