---
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


---

# Assign responsibilities

# Assign responsibilities {#ariaid-title1}

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

Use the responsibility data model to assign responsibilities to a service
organization (SO) member.

## Antes de Iniciar

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Businesses often need staff to work at more than one business location, and they can have different responsibilities at different locations. Using the responsibility data model, an SO member can be assigned multiple
responsibilities.  
The responsibility data model tracks the relationship between the SO members and their responsibility type in the Service Organization Member Responsibilities \[sn_csm_svc_org_member_responsibility\] table.  
Nota:  
If the business location plugin is active, this feature is enabled by default. However, for upgrade customers, the data in the \[sn_csm_svc_org_member_responsibility\] table will be auto-populated for existing SO members to confirm that they retain as much access after the upgrade. Any new records created after the Australia release must be created using the following steps.

## Procedimento

1. Navigate to AllCustomer ServiceService OrganizationsInternal/External Business Locations.
2. Open the business location (internal or external) record.
3. Open the SO Member record from the Members related list.
4. Select New to create a record in the SO Member Responsibilities \[sn_csm_svc_org_member_responsibility\] table.  
   The Organization Member Responsibility record shows the following fields: Member, Type, and Order.  
   Nota:  
   The Member field refers to the \[sn_csm_service_organization_member\] table. This field is auto-populated if the record is initiated from the SO Member related list. The Type field refers to the \[sn_customerservice_related_party_configuration\] table, and the Order field specifies the sequence in which records are displayed, organized according to business preferences.  
   With the base system, users with a specific role can be assigned a particular type.{#csm-assign-responsibilities__table_wzl_3yr_ptb__entry__2}

   | Responsibility | Name |
   |-|-|
   | Location Agent Nota: This role only applies to the internal business location. | sn_customerservice.svc_location_agent |
   | Location Consumer Agent Nota: This role only applies to the internal business location. | sn_customerservice.svc_location_consumer_agent |
   | Location Contributor | sn_customerservice.service_organization_contributor |
   | Location Manager Contributor | sn_customerservice.svc_location_manager_contributor |
   | Location Manager Fulfiller Nota: This role only applies to the internal business location. | sn_customerservice.svc_location_manager |
   | Location Relationship Manager Nota: This role only applies to the external business location. | sn_bus_loc.location_relationship_manager |
   | Location Support Agent | sn_bus_loc.svc_location_support_agent |
   [Tabela 1. User roles and associated types]

   {#csm-assign-responsibilities__table_wzl_3yr_ptb}
5. After you assign the required related party type, select Submit.  
   A new responsibility is added to the SO member.

