Interested in a ServiceNow event built for developers? Registration for now[dev]26 is officially open!

How to limit the content manager role to specific topics

heathers_
Kilo Sage

I've reviewed the Employee Academy sessions but am running into a roadblock.

 

We require the content manager to be scoped at the topic level. An HR Benefits content manager should not be able to checkout, edit, publish content on any other topic.

 

I've granted Content Publishing access through the topic however the users are able to edit content on all topics.

heathers__2-1741713519983.png

Example: Should not have access to the IT topic.

heathers__1-1741713458478.png

 

 

4 REPLIES 4

Shivalika
Mega Sage

Hello @heathers_ 

 

Please make use of user criteria for limiting the access for particular topics. 

 

Kindly mark my answer as helpful and accept solution if it helped you in anyway,

 

Regards,

Shivalika 

 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

 

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY

Not applicable

Hi @heathers_ ,

 

On the particular Topic, you can use a checkbox called "Enable user criteria check",once you check it, you can see two other fields called available for and Not available for, where you can create a User criteria and provide the access.

SandeepDutta_0-1742011642374.png

 

ChristinaMillr1
Tera Contributor

Did you find a resolution to this issue? I am facing a similar issue. I created a group with thesn_cd.content_manager role, and assigned that group to a topic.  The publishing capabilities works at the topic level, but is also allowing them to edit all news articles. 
User criteria is not the solution for this use case - user criteria is meant to control access to the topic on EC, not publishing abilities. 

FWIW - We did the following to support our use case:
1. Enabled "Allow Ownership for Portal Pages" to be able to add users or groups to the page itself.
The option can be enabled from the Content Publishing Properties page:
Content Publishing > Advanced > Properties

2. Created a group for what we will call our "content admins" - people we want to be able to edit ALL content

2. Created content topic groups for each topic, who needs to be able to edit specific content

3. Automatically assign the content admin group to the 'Restrict Content by Group' related list every time content is published.

4. Manually add individuals or content topic groups as needed to the Restrict Content by Group / Individual related list.

 

If you don't have an overarching team that needs to own / edit ALL content, then you can skip step 3. 

 

https://www.servicenow.com/docs/r/employee-service-management/employee-experience-foundation/ecpro-p...