---
sourceDocument: Brazil Sales Customer Relationship Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/order-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Sales Customer Relationship Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Related parties, access, responsibilities

# Related parties, responsibilities, and access included with Sales Common {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Related parties, responsibilities, and access included with Sales Common

The Sales Common (snsalescommon) app in ServiceNow provides default related party configurations, responsibilities, and access levels designed to manage user roles and permissions effectively within sales processes.
This setup is essential for controlling access to opportunities, accounts, contacts, quotes, and other CRM records based on user responsibilities.
Show full answer Show less  

## Default Related Parties and Responsibilities

The app includes key related parties with associated responsibilities focused on sales functions:

* **Account Executive** -- Applies to Territory and Opportunity entities.
* **Price Band Approver** -- Applies to Territory and Opportunity entities, responsible for price band review and approval.
* **Solution Sales Executive** -- Applies to Territory and Opportunity entities, involved in solution selling.

Each related party configuration corresponds to a User entity (sysuser).

## Responsibility Access Configuration

Responsibilities use access configurations to define the scope of data accessible by users. Access is granted only if the user has the required role and is linked to the record through a defined relationship table:

* **Required Role:** `salesrestrictedagent (snsalescommon.salesrestrictedagent)` for all default responsibilities.
* **Relationship Tables:** Opportunity Team Member \[snoptymgmtcoreopportunityteammember\] or Territory Membership Responsibility \[sntpcrmextnterritorymembershipresponsibility\].

**Note:** The Sales Territory Management plugin must be installed to use Territory Membership Responsibility.

## Access Levels by Responsibility

* **Account Executive:**
  * Read/write access to Account and Consumer records.
  * Full access (read/write/create) to Account Address, Account Team Member, Contact, and Quote.
  * Opportunity and Opportunity Allocation access varies by relationship table, ranging from read/write to full access.
* **Solution Sales Executive:**
  * Read access to Account, Account Address, Account Team Member, Consumer, Contact, and Opportunity Allocation.
  * Full access to Quote.
  * Opportunity access depends on relationship table and ranges from read/write to full access.
* **Price Band Approver:**
  * Read-only access to Account, Account Address, Account Team Member, Consumer, Contact, Opportunity, Opportunity Allocation, and Quote.

## Customization

Customers can choose to use these default configurations or create custom responsibility access configurations that better fit their organizational access requirements. This includes defining new responsibilities and related party configurations to tailor access control within their sales processes.  
Default related party configurations, responsibilities, and access levels included with the Sales Common
app.

## Default related parties and responsibilities {#responsibilities-sales-automation__section_idr_pmw_fkc}

The following related parties and responsibilities are available with the Sales Common (sn_sales_common) app.
{#responsibilities-sales-automation__table_related_party_config__entry__3}

| Related party configuration | Applies to | Default responsibility |
|-|-|-|
| Account Executive | * Territory \[sn_tp_territory\] * Opportunity \[sn_opty_mgmt_core_opportunity\] {#responsibilities-sales-automation__ul_bvg_4gr_fkc} | Account Executive |
| Price Band Approver | * Territory \[sn_tp_territory\] * Opportunity \[sn_opty_mgmt_core_opportunity\] {#responsibilities-sales-automation__ul_zwf_pgr_fkc} | Price Band Approver |
| Solution Sales Executive | * Territory \[sn_tp_territory\] * Opportunity \[sn_opty_mgmt_core_opportunity\] {#responsibilities-sales-automation__ul_eg3_pgr_fkc} | Solution Sales Executive |
[Table 1. Default related parties and responsibilities]

{#responsibilities-sales-automation__table_related_party_config}

The entity type for every related party configuration listed here is User \[sys_user\].

## Responsibility Access Configuration fields {#responsibilities-sales-automation__section_n5g_pls_fkc}

Use responsibility access configurations to define what each responsibility can access. For the list of Responsibility Access Configuration form fields, see [Configure access through the responsibility access configuration](https://www.servicenow.com/docs/access?context=declarative-resposibility-framework&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US).

## Responsibility access summary {#responsibilities-sales-automation__section_hxh_3ls_fkc}

The following table summarizes how the default responsibilities are used for responsibility-based access. Access is granted only when the user has the required role and is connected to a record through the configured relationship
table.
{#responsibilities-sales-automation__table_fbr_jls_fkc__entry__4}

| Responsibility | Used through relationship | Required role | Typical access intent |
|-|-|-|-|
| Account Executive | Opportunity Team Member or Territory Membership Responsibility | sales restricted agent \[sn_sales_common.sales_restricted_agent\] | Grants working access to opportunities and related CRM records, such as accounts, contacts, quotes, and opportunity allocations. |
| Solution Sales Executive | Opportunity Team Member or Territory Membership Responsibility | sales restricted agent \[sn_sales_common.sales_restricted_agent\] | Grants access to opportunities and related CRM records for solution selling responsibilities. |
| Price Band Approver | Opportunity Team Member or Territory Membership Responsibility | sales restricted agent \[sn_sales_common.sales_restricted_agent\] | Grants visibility to opportunities and related records that require price band review or approval. |
[ ]

{#responsibilities-sales-automation__table_fbr_jls_fkc}  
Note:  
The Sales Territory Management plugin must be installed on your instance to configure or use Territory Membership Responsibility.  
Each of the following responsibility uses the sales restricted agent (sn_sales_common.sales_restricted_agent) role and is active by default, through either relationship table:

* Opportunity Team Member \[sn_opty_mgmt_core_opportunity_team_member\]
* Territory Membership Responsibility \[sn_tp_crm_extn_territory_membership_responsibility\]
{#responsibilities-sales-automation__ul_xfm_jms_fkc}

Account Executive
:
    The Account Executive gets the following access:

    * Read and write access to Account and Consumer.
    * Read, write, create, and full access to Account Address, Account Team Member, Contact, and Quote.
    {#responsibilities-sales-automation__ul_yfm_jms_fkc}

    Access to Opportunity and Opportunity Allocation depends on the relationship table, listed in the following table.{#responsibilities-sales-automation__table_zfm_jms_fkc__entry__3}

    | Accessible table | Via Opportunity Team Member | Via Territory Membership Responsibility |
    |-|-|-|
    | Opportunity | Read, write | Read, write, create, full |
    | Opportunity Allocation | Read | Read, write, create, full |
    [Table 2. Account Executive access that depends on the relationship table]

    {#responsibilities-sales-automation__table_zfm_jms_fkc}

Solution Sales Executive
:
    The Solution Sales Executive gets read access to Account, Account Address, Account Team Member, Consumer, Contact, and Opportunity Allocation, and read, write, create, and full access to Quote, through either relationship table. Access to Opportunity depends on the relationship table, listed in the following table.{#responsibilities-sales-automation__table_agm_jms_fkc__entry__3}

    | Accessible table | Via Opportunity Team Member | Via Territory Membership Responsibility |
    |-|-|-|
    | Opportunity | Read, write | Read, write, create, full |
    [Table 3. Solution Sales Executive access that depends on the relationship table]

    {#responsibilities-sales-automation__table_agm_jms_fkc}

Price Band Approver
:   Price Band Approver gets read-only access to Account, Account Address, Account Team Member, Consumer, Contact, Opportunity, Opportunity Allocation, and Quote, through either relationship table.

## Custom responsibility access configurations {#responsibilities-sales-automation__section_ojr_4ns_fkc}

You can use the default configurations provided with Sales Common or create additional responsibility access configurations based on your organization's access requirements. For more information, see:

* [Create a responsibility definition](https://www.servicenow.com/docs/access?context=t_CreateAResponsibilityDefinition&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US)
* [Creating a responsibility access configuration](https://www.servicenow.com/docs/access?context=creating-responsibility-access-configuration&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US)
* [Create related party configurations](https://www.servicenow.com/docs/access?context=adding-related-party-config-to-case&version=brazil&pubname=brazil-customer-service-management&ft:locale=en-US)
{#responsibilities-sales-automation__ul_bgm_jms_fkc}

