---
sourceDocument: Yokohama Customer Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/customer-service-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Customer Service Management

ft:clusterId :

    - csm

bundleId :

    - csm

workflow :

    - Customer and Industry


---

# Configure access through the responsibility access configuration

# Configure access through the responsibility access configuration {#ariaid-title1}

Release version: Yokohama  
Updated January 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Streamline how you create and update your responsibility definitions and access configurations by using the declarative responsibility framework in the Customer Service Management (CSM) application. This framework enables you to select the level of access for each responsibility by leveraging low-code or no-code capabilities, which reduces the time required for scripting.

## Before you begin

Role required: admin

## About this task

The Responsibility Access Configuration \[sn_customerservice_responsibility_access_config\] table is used to store the metadata of the responsibility access configuration. This configuration specifies the level of access and the
entities that can be accessed by a particular responsibility. For more information about creating a responsibility definition, see [Create a responsibility definition](https://servicenow-prod.fluidtopics.net/SaNEdU9W5pzB~Oe8OtGjbw "A responsibility, or responsibility definition, specifies the role or function a user has within an entity, determining access through relationships. When creating a relationship, users are assigned specific responsibilities that grant access to the entity and its related entities."). The need for domain separation in configuring access records is determined by the domain of the referenced responsibility.  
Note:  
Starting with the Yokohama release, creating and updating responsibility definitions and access configurations using the declarative responsibility framework is deactivated.