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


---

# Responsibility-based access to Sales CRM entities

# Responsibility-based access to Sales CRM entities {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Responsibility-based access to Sales CRM entities

Responsibility-based access in Sales CRM enables users to access records such as opportunities, accounts, and sales territories based on the specific responsibilities they hold.
This approach restricts users from having broad access and instead scopes record visibility to those connected to their assigned roles within opportunity teams or sales territories.
This ensures users see only relevant leads, opportunities, contacts, quotes, or CRM Touchpoints aligned with their responsibilities.
Show full answer Show less  

## How Access is Granted

Sales CRM supports two main access patterns:

* **Blanket Access:** For users with broad roles (e.g., lead writer or CRM touchpoint writer), granting full access to all records of a type.
* **Responsibility-based Access:** For users assigned specific roles such as Account Executive or Price Band Approver, restricting access only to records tied to their responsibilities in opportunity teams or sales territories.

Users with the **sales restricted agent** role can only view and manage CRM records linked to their responsibilities.

## How Responsibility-based Access Works

Access is determined through multiple configuration layers:

* **Related party configuration:** Defines the business relationship a user has with a CRM record (e.g., Account Executive).
* **Relationship tables:** Store connections between users and records, such as the Opportunity Team Member and Territory Membership Responsibility tables.
* **Responsibility definition:** Specifies the responsibility assigned to the user.
* **Responsibility access configuration:** Maps responsibilities to accessible tables, access levels (read, write, create), required roles, and relationship paths.
* **Required role:** Confirms user has the necessary role (e.g., sales restricted agent) for access to apply.

Access to records is granted only when all these conditions align, ensuring fine-grained control based on user responsibility and role.

## Relationship and Accessible Tables

Relationship tables identify where user responsibilities are recorded, primarily:

* **Opportunity Team Member:** Grants access based on opportunity team membership.
* **Territory Membership Responsibility:** Grants access based on sales territory membership.

A responsibility can grant access to multiple accessible tables like Opportunity, Account, Contact, Quote, CRM Touchpoints, and others, each potentially with different access levels and filters. This flexibility allows administrators to tailor access precisely to business needs.

## CRM Touchpoints and Granular Roles

CRM Touchpoints require specific granular roles to be accessible through the responsibility framework:

* **CRM touchpoint responsibility read granular:** Enables read access.
* **CRM touchpoint responsibility write granular:** Enables write access (includes read access).

Administrators must update responsibility access configurations to include CRM Touchpoints and assign the appropriate granular roles to users, ensuring they have the correct levels of access to CRM Touchpoints based on their responsibility.

## Practical Implications for ServiceNow Customers

* Use responsibility-based access to limit user visibility to only relevant sales records, enhancing security and data relevance.
* Configure responsibilities, relationship tables, and access levels carefully to match your sales organization's roles and workflows.
* Assign the necessary roles such as **sales restricted agent** and granular CRM Touchpoint roles to ensure users can access required records without overexposure.
* Leverage filters on accessible tables to further refine record visibility by type, state, or other criteria.

By implementing responsibility-based access, you provide your sales teams with tailored data access that aligns with their duties while maintaining data security and governance within the Sales CRM environment.  
Responsibility-based access grants Sales CRM users access to records based on the responsibility they hold for an opportunity, account, or sales territory. Instead of giving users broad access to every lead, opportunity, account,
contact, quote, or CRM Touchpoints, the responsibility framework scopes access to records connected to the user's opportunity team or sales territory membership.

## How users get access to Sales CRM records {#responsibility-based-access-crm-touchpoints__section_iph_53f_zjc}

Sales CRM supports the following access patterns:

* Blanket access: Users with broad roles, such as the lead writer \[sn_lead_mgmt_core.lead_writer\] or CRM touchpoint writer \[sn_crm_touchpoint.touchpoint_writer\] role, can view or work with every record of that type, regardless of the opportunity, account, or sales territory that the record is associated with. Use this access pattern for users who need broad visibility across sales records.
* Responsibility-based access: Users get access based on the responsibility they hold in a sales territory or on an opportunity team. For example, users can be added as Account Executives, Solution Sales Executives, or Price Band Approvers. The responsibility framework uses those memberships to grant access only to the records that are connected to the user's responsibility. Multiple users can hold different responsibilities within the same territory. Different users can join an opportunity team, such as an overlay sales representative or a Solution Sales Executive from outside the opportunity's territory.
{#responsibility-based-access-crm-touchpoints__ul_e21_kxr_fkc}

Users with the sales restricted agent \[sn_sales_common.sales_restricted_agent\] role can see and manage only the CRM records that are connected to what they are responsible for.

## How responsibility-based access works {#responsibility-based-access-crm-touchpoints__section_wwq_pkf_zjc}

Responsibility-based access uses multiple configuration layers to determine whether a user can access a record.{#responsibility-based-access-crm-touchpoints__table_jzr_fzr_fkc__entry__3}

| Configuration element | Description | Example |
|-|-|-|
| Related party configuration | Defines the business relationship that a user can have with a CRM record. | Account Executive, Solution Sales Executive, Price Band Approver |
| Relationship table | Stores the record that connects the user to an opportunity or sales territory. | * Opportunity Team Member \[sn_opty_mgmt_core_opportunity_team_member\] table * Territory Membership Responsibility \[sn_tp_crm_extn_territory_membership_responsibility\] table {#responsibility-based-access-crm-touchpoints__ul_fz3_rzr_fkc} |
| Responsibility definition | Defines the responsibility assigned to the user through the relationship. | Account Executive |
| Responsibility access configuration | Defines which tables the responsibility can access, the access level for each table, the required role, and the relationship path. | Account Executive can read and write Opportunity records |
| Required role | Confirms that the user has the necessary role required for the configuration to apply. | Sales restricted agent \[sn_sales_common.sales_restricted_agent\] role |
[Table 1. Configuration layers for responsibility-based access]

{#responsibility-based-access-crm-touchpoints__table_jzr_fzr_fkc}

When these conditions match, the user receives the configured access to records in the accessible table.

## Relationship between related party and responsibility {#responsibility-based-access-crm-touchpoints__section_gsp_q1s_fkc}

A related party describes the user's business relationship to a record. A responsibility determines what access the user can receive because of that relationship.

For example, when a user is added to an opportunity as an Account Executive, the record on the Opportunity Team Member \[sn_opty_mgmt_core_opportunity_team_member\] table connects the user to the opportunity. The Account Executive
responsibility then determines which related CRM records the user can access, such as the opportunity, account, contact, quote, or CRM Touchpoints records.

The responsibility name alone does not grant access. Access is granted only when a responsibility access configuration maps the responsibility to an accessible table, access level, required role, and relationship table.
Figure 1. Related Party Configurations available with the Sales Common app

## Example: Account Executive access {#responsibility-based-access-crm-touchpoints__section_kkv_bbs_fkc}

The Account Executive responsibility can have multiple responsibility access configuration records. Each configuration grants access to one accessible table through a specific relationship table.
Figure 2. Responsibility Definition and Responsibility Access Configurations

For example, if a user is connected to an opportunity through the Opportunity Team Member
\[sn_opty_mgmt_core_opportunity_team_member\] table and has the Account Executive responsibility, the responsibility access configuration can grant the user read and write access to the Opportunity tables. Other configuration rows can
grant access to related tables, such as Account, Contact, Quote, Account Address, Consumer, and Opportunity Allocation.

Access levels apply to records in the accessible table, not to the responsibility or relationship
table. For example, if the accessible table is Leads and the access levels are Read, Write, and Create, users with the matching responsibility and required role can read, update, and create quote records that are reachable through
the configured relationship.

## Relationship tables {#responsibility-based-access-crm-touchpoints__section_dsc_4bs_fkc}

The relationship table identifies where the user's responsibility is recorded. In Sales CRM, responsibility-based access typically uses one of these relationship paths:{#responsibility-based-access-crm-touchpoints__table_jys_pbs_fkc__entry__2}

| Relationship path | When it applies |
|-|-|
| Opportunity Team Member \[sn_opty_mgmt_core_opportunity_team_member\] | Grants access based on a user's responsibility on an opportunity team. |
| Territory Membership Responsibility \[sn_tp_crm_extn_territory_membership_responsibility\] | Grants access based on a user's responsibility in a sales territory. |
[Table 2. Relationship tables for Responsibility Access Configuration in Sales CRM]

{#responsibility-based-access-crm-touchpoints__table_jys_pbs_fkc}

For example, opportunity-based access uses the Opportunity Team Member relationship path to determine whether a user is connected to the opportunity. Territory-based access uses the Sales Territory Member relationship path to
determine whether a user is connected to the territory.

## Accessible tables {#responsibility-based-access-crm-touchpoints__section_s3h_vbs_fkc}

The accessible table is the table on which access is being granted. A single responsibility can have multiple responsibility access configuration records, each for a different accessible table. For example, the Account Executive responsibility can grant different levels of access to these accessible tables:

* Opportunity
* Account
* Account Team Member
* Account Address
* Contact
* Consumer
* Quote
* Opportunity Allocation
* CRM Touchpoints
{#responsibility-based-access-crm-touchpoints__ul_eqr_ybs_fkc}

Each accessible table can have its own access level and optional filter. This lets administrators grant broader access to some records and more limited access to others.

## CRM Touchpoints access through the responsibility framework {#responsibility-based-access-crm-touchpoints__section_hbf_1cs_fkc}

The sales restricted agent \[sn_sales_common.sales_restricted_agent\] role inherits the lead and opportunity responsibility granular roles by default. Therefore, the responsibility framework can evaluate access to lead and opportunity records. Other CRM entities need their own granular roles added before the framework can evaluate access to them. For example, on CRM Touchpoints, the following granular roles make CRM Touchpoints available to the framework:

* CRM touchpoint responsibility read granular \[sn_crm_touchpoint.touchpoint_responsibility_read_granular\]: Provides read access to CRM Touchpoints through the responsibility framework.
* CRM touchpoint responsibility write granular \[sn_crm_touchpoint.touchpoint_responsibility_write_granular\]: Provides write access to CRM Touchpoints through the responsibility framework. This role includes the read granular role.
{#responsibility-based-access-crm-touchpoints__ul_o2r_2cs_fkc}

To extend CRM Touchpoints access to a responsibility definition, such as Account Executive or Solution Sales Executive, an administrator updates or creates a responsibility access configuration for that responsibility. The
administrator selects CRM Touchpoints \[sn_crm_touchpoint_touchpoint\] as the accessible table, selects the access levels, and optionally adds an accessible table filter to limit access by type, state, or another condition. For more
information, see [Create a responsibility access configuration in Sales CRM](https://servicenow-prod.fluidtopics.net/gpuX1hxPdjwaJCFTYMfmLQ "Grant a responsibility definition table-level access to leads, opportunities, and related entities by creating or updating a responsibility access configuration.").

For example, an administrator can configure the Solution Sales Executive responsibility so that users can edit only CRM Touchpoints of type Solution review while other CRM Touchpoints types remain read-only.  
Note:  
Administrators who assign persona roles such as Solution Sales Executive or Account Executive must also ensure that sales restricted agent \[sn_sales_common.sales_restricted_agent\] role includes the CRM touchpoint responsibility write granular \[sn_crm_touchpoint.touchpoint_responsibility_write_granular\] role for the intended access.
**Related reference**   

* [Components installed with Sales Common](https://servicenow-prod.fluidtopics.net/sGK9bRYDWkB6dl~Xfyrxtw "Several types of components are installed with activation of the Sales Common (sn_sales_common) plugin, including user roles and tables.")
* [Components installed with CRM Touchpoints](https://servicenow-prod.fluidtopics.net/ZNfF6M3cIw3hwEoCb1idKQ "Several types of components are installed with activation of the CRM Touchpoints plugin, including tables and user roles.")
* [Related parties, responsibilities, and access included with Sales Common](https://servicenow-prod.fluidtopics.net/26inMtt2tNWulWP_NsC7lw "Default related party configurations, responsibilities, and access levels included with the Sales Common app.")

