---
sourceDocument: Australia Sales Customer Relationship Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/order-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia 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: Australia  
Updated August 14, 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 configurations for related parties, responsibilities, and access levels tailored for sales processes.
These configurations facilitate role-based access control to key sales records such as opportunities, accounts, contacts, quotes, and related allocations, ensuring that users have appropriate permissions based on their responsibilities within sales territories or opportunities.
Show full answer Show less  

## Default Related Parties and Responsibilities

* **Account Executive**: Associated with Territory and Opportunity entities; responsible for managing sales accounts and opportunities.
* **Price Band Approver**: Linked to Territory and Opportunity; responsible for reviewing and approving price bands on sales opportunities.
* **Solution Sales Executive**: Related to Territory and Opportunity; handles solution selling responsibilities.

All related parties use the **User \[sysuser\]** entity type.

## Responsibility Access Configuration

Access for these responsibilities is controlled via responsibility access configurations that define what records each role can access. Access is granted only when the user has the required role and is linked to the record through configured relationships such as Opportunity Team Member or Territory Membership Responsibility.

## Key Responsibilities and Access Details

* **Account Executive** : Uses the `salesrestrictedagent` role. Grants read/write access to accounts and consumers, and full access to account addresses, team members, contacts, and quotes. Opportunity and opportunity allocation access varies based on relationship type.
* **Solution Sales Executive** : Also using the `salesrestrictedagent` role, has read access to many sales-related records and full access to quotes. Opportunity access depends on relationship type.
* **Price Band Approver**: Has read-only access to key sales records related to opportunities requiring approval.

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

## Customizing Responsibility Access

ServiceNow customers can use these default responsibility and access configurations or create custom definitions tailored to their organization's sales processes and security requirements. This flexibility allows precise control over who can view or modify sales records based on their roles and relationships.  
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=australia&pubname=australia-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=australia&pubname=australia-customer-service-management&ft:locale=en-US)
* [Creating a responsibility access configuration](https://www.servicenow.com/docs/access?context=creating-responsibility-access-configuration&version=australia&pubname=australia-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=australia&pubname=australia-customer-service-management&ft:locale=en-US)
{#responsibilities-sales-automation__ul_bgm_jms_fkc}