List of related party configurations provided with the base system
Summarize
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 List of related party configurations provided with the base system
This document outlines the default related party configurations included in the base ServiceNow system as of the Australia release version updated July 20, 2026. It details the standard types and their associated default responsibilities across various entities such as cases, sold products, install bases, account team members, contact relationships, consumer relationships, household member relationships, and service organizations.
Show less
Key Features
- Related Party Configurations by Entity: Each entity type (e.g., cases, sold products, install bases) has predefined related party types and corresponding default responsibilities to streamline role assignment.
- Responsibility Auto-Population: When a related party record is created, the Responsibility field is automatically populated based on the default responsibility tied to the selected party type.
- Order Field Auto-Population: Similarly, the Order field is auto-filled according to the default order of the party type, ensuring consistent hierarchy and processing.
- Listed Role Types: These roles exist but do not have any responsibility assigned by default, and therefore, do not grant access rights unless responsibility is explicitly specified.
- Access Control Based on Responsibility: Access permissions depend on the Responsibility field; related parties without a responsibility assigned will not have access.
Practical Application for ServiceNow Customers
- Understand the predefined related party roles and responsibilities for different entities to efficiently manage stakeholder relationships within your ServiceNow environment.
- Leverage the automatic assignment of responsibilities and order to reduce manual data entry errors and ensure consistent role management.
- Recognize that listed roles act as placeholders without default responsibilities and therefore do not confer access privileges, helping to maintain security and proper access control.
- For install bases, refer to the additional guidance provided on adding related parties to install base items to fully utilize these configurations.
Default Related Party Configuration Highlights
- Cases: Roles like Authorized Contact, Authorized Representative, Authorized Consumer, and Authorized Contributor primarily default to Authorized Representative responsibility.
- Sold Products: Key roles such as Authorized Account and Authorized Contact default to Authorized Account and Authorized Representative responsibilities, respectively.
- Install Bases: Multiple roles including Authorized Account, Contact, Consumer, Contributor, Member, and Service Organization default to Authorized Representative or Authorized Service Organization responsibilities.
- Account Team Members: Defined roles include Account Manager, Preferred Technician, Primary Support Agent, and Support Manager, each with corresponding default responsibilities matching their role names.
- Contact and Consumer Relationships: Default responsibilities align with their role names such as Asset Contact and Authorized Representative.
- Household Member Relationships: Roles default to Authorized Representative responsibility.
- Service Organizations: Roles such as Location Agent, Location Consumer Agent, Location Contributor, Location Manager, Location Fulfiller, and Location Support Agent have specific default responsibilities to cover various organizational functions.
Related party configurations for different entities that are provided with the base system are listed in the following tables.