---
sourceDocument: Australia Customer Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/customer-service-management

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Customer Service Management

ft:clusterId :

    - csm

bundleId :

    - csm

workflow :

    - Customer and Industry


---

# Configure responsibility access

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

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

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.

## Antes de Iniciar

Role required: One of the following roles:

* sn_crm_customer_access_management_admin
* sn_crm_foundation_admin
* admin
{#declarative-resposibility-framework__ul_qvq_msx_m3c}

## Por Que e Quando Desempenhar Esta Tarefa

The Responsibility Access Configuration \[sn_customerservice_responsibility_access_config\] table is used to store the metadata of the responsibility access configuration. With this configuration, you can enable different levels of
access for related party users across different records of the same entity. For example, a user with a location manager role might serve as a fulfiller at one business location and as an agent at another.

For more information about creating a responsibility definition, see [Create a responsibility definition](https://servicenow-prod.fluidtopics.net/RAa0PJmIgP1j4PHADVvJJA "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.

## Procedimento

1. Navigate to AllCustomer ServiceAdministrationResponsibility Definitions.
2. Select a responsibility definition record.
3. From the Responsibility Access Configuration related list, select New.
4. On the form, fill in the fields.  
   {#declarative-resposibility-framework__table_xqp_24b_1yb__entry__2}

   | Field | Description |
   |-|-|
   | Responsibility | Responsibility applicable to this configuration, for example, account manager or authorized representative. |
   | Active | Status of the configuration. By using this functionality, you can enable or disable a responsibility access configuration. The default value is True. |
   | Roles required | Roles required in addition to responsibilities to get the access. |
   | Description | Provides a description of the purpose or function of the responsibility access configuration. |
   | Access levels | Levels of access for the accessible entities. The list shows the access levels, including read, write, and full. Nota: Full represents a special access level that is equivalent to read, write, and create. |
   | Accessible table | Entities or records accessible through this configuration, like cases or sold products. |
   | Accessible table filter | Additional conditions to filter the accessible table. |
   | Relationship table | Relationship table where this configuration is applied, for example account team member \[sn_customerservice_team_member\] table. |
   | Relationship filter | Additional conditions to filter the relationship record applicable to the user. |
   | Type | Type of association between the accessible and relationship table. Listed are three types of association: * Simple * Dependent * Advanced {#declarative-resposibility-framework__ul_xtv_wc4_bgc} |
   | Relationship field | Field on the relationship table to be used for association. |
   | Accessible table field | Field on the accessible table to be used for association. |
   | Dependent table | Table that contains the mapping between the relationship field and accessible table field. |
   | Dependent relationship field | Field on the dependent table that maps to the selected relationship field. |
   | Dependent accessible table field | Field on the dependent table that maps to the selected accessible table field. |
   | Field values script | Script that returns the valid association values for advanced association logic. |
   | Description | Provides a description of the purpose or function of the responsibility definition. |
   [Tabela 1. Responsibility Access Configuration form fields]

   {#declarative-resposibility-framework__table_xqp_24b_1yb}  
   Nota:  
   To create entries to the Applies to Relationship, Access Levels, or Accessible Entities fields in the Responsibility Access Configuration table, you must migrate all existing configurations for these fields in the global.CSMRelationshipConstantsSNC script include.
5. Select Submit.
{#declarative-resposibility-framework__steps_rmt_bl4_bgc}