---
sourceDocument: Xanadu Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/employee-service-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Configure additional permission levels for topic management

# Configure additional permission levels for topic management {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Experience decentralized management of topics by configuring two new permission
levels, topic manager and topic contributor.

## Before you begin

Role required: taxonomy_admin

## About this task

Use distributed topic management by establishing two new user criteria,
Topic manager and Topic contributor. These roles are additional levels of control introduced
along with the existing Taxonomy admin, Taxonomy manager, and Taxonomy
contributors.

## Procedure

1. Navigate to AllContent TaxonomyTopics.
2. Select the desired topic within a taxonomy and define the user criteria, namely Topic manager, and Topic contributor.

## Result

Admins can configure additional permission levels to delegate topic management level
tasks to these two user criteria. For more information on these two user criteria,
see [Topic managers and contributors for topic page management](https://servicenow-prod.fluidtopics.net/ZvvbdW7Cv02yvHHhGqYGrA "While topic managers control the topic level decisions, the contributors manage the connected content, quick links, adding applications, and featured content on the topic page.").

## What to do next

Note:  
* Any number of personae could be added to both the permission levels. Additional permissions provided at a topic level are additive, not overriding.
* Access flows from the root topic to its sub-tree in a top-down manner. Topic manager and Topic contributor can only make changes from the level
  they have been provided access to and further down the
  sub-tree.

{#add-additional-permission-levels-for-topic-management__ul_xpf_3vc_qtb}

*[\>]: and then