---
sourceDocument: Brazil Governance, Risk, and Compliance
sourceDocumentLink: https://www.servicenow.com/docs/r/governance-risk-compliance

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Entities

# Entities in GRC {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 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 Entities in GRC

In Governance, Risk, and Compliance (GRC), an entity represents a person, process, department, application, or object whose risk exposure must be managed and monitored.
Defining entities allows organizations to maintain accountability by assigning each entity an owner and applying appropriate controls.
Entities can have hierarchical relationships, with upstream (parent) and downstream (child) entities.
When source records linked to entity filters are created, entities are generated automatically, with options to synchronize entity names and owners to the source records for accurate tracking.
Show full answer Show less  

## Entity Management and Synchronization

Entities are automatically created when linked source records are generated in GRC. Synchronization between entity names and owners with their source records can be controlled using a synchronization checkbox at the entity level. Selecting this checkbox locks these fields to stay aligned with the source record. Continuous synchronization is maintained by a scheduled job, configurable by frequency (daily, weekly, or monthly) and batch size, ensuring up-to-date entity information vital for compliance tracking.

## Entity Classes

Entity classes serve to categorize or tag entities conceptually, such as grouping office branches by location. These classes are associated with entity tiers that define hierarchical levels for better organization and prioritization. Entity class rules automate the assignment of classes to new entities created on specific tables, streamlining entity classification and management.

## Entity Types

Entity types group entities based on defined filters, enabling efficient identification and management of entities matching specific criteria. They support hierarchical relationships within entity classes and facilitate the creation of risks and controls tailored to each entity group. For example, multiple departments like Finance, HR, and IT can be grouped under an entity type called Departments, linked to core business pillars such as Technologies or Facilities.

## Entity Tiers

Entity tiers establish hierarchical levels for entity classes, applying a prioritization that helps organizations focus on the most critical items. This tiered structure enhances visibility into entity status and supports targeted risk management efforts.  
In Governance, Risk, and Compliance, an entity can be a person, process, department, application, or object, whose exposure must be managed. These entities have controls that are defined to view the status.

To understand entities, consider the following example. Assume that you're a new GRC user and you want to implement a change management process to all your critical financial systems. All the systems can be considered as individual entities. Map all the systems to an entity class called
Financial. Have an entity type filter for critical financial systems to determine the systems that are identified as critical.

The primary benefit of creating entities is that you can maintain accountability because each entity has an owner. To understand this benefit, assume that you want to configure all the servers in a new way. After you finish the
configuration, you perform an audit and then discover that only one server failed to comply with the new configuration. If you had not defined all the entities, then the entire audit result would have been deemed as failed. But
because you have the entities defined, then only the non-compliant server entity and its identified owner are held accountable instead of all the servers.

Having defined entities ensures that the entity owners can be identified and that appropriate controls can be applied to those entities. It also helps in tracking the entities that are non-compliant. Any entity that has child
entities can be said to have downstream entities. Any entity that has parent entities can be said to have upstream entities.

When a source record linked to an entity filter is created, an entity is automatically generated in GRC. If the source record name or owner changes after the entity is created, the entity name and owner
can update to match the source record.

You can control this synchronization at the entity level using the Sync entity name and entity owner with source record check box. When selected, the Name and Owner fields become read only and stay in synchronization with the
source record. Clearing the check box enables you to manually override the entity name and owner.  
The actual synchronization work is performed by a scheduled job called Sync entity name and entity owner with source record. When an entity is first created, the synchronization happens automatically. For continuous synchronization of future changes to source records, this scheduled job must be active. The job syncs entity names and owners based on GRC properties that control its behavior:

* Frequency of syncing the entity name and entity owner with the source record: Determines how often the job runs (options: daily, weekly, monthly). Based on the selected frequency, the synchronization occurs at regular intervals.
* Maximum batch size while syncing the entity name and entity owner with the source record: Controls the number of records processed in each batch.
{#what-is-an-entity__ul_ybv_sww_h3c}

After creating entities, you can tag the similar entities by defining the entity class for them individually or you can link them to an existing entity class.

## Entity classes {#what-is-an-entity__section_wmn_333_qqb}

Entity classes are used to add a conceptual information about the entity or tag the entity. To understand the concept of entity class, consider the following example. A company has office branches in three cities. The office space is considered as an entity and the entity class for these entities would be the location. You can create an entity class by associating it with an entity tier as shown in the following example.Figure 1. Sample configuration for an entity class

## Entity class rules {#what-is-an-entity__section_pjy_m33_qqb}

Entity class rules help to assign classes to the entities at the table level. Any new entity created on the table gets that entity class automatically. Entity classes are used to tag your entities.

When you create an entity over a specific table, the class associated with that table automatically gets assigned to the entity. You can set a new entity class rule for a table.

## Entity types {#what-is-an-entity__section_kkk_p33_qqb}

An entity type is a grouping of entities that is based on filtering. Entity types enable you to find and create entities that match a set of filter conditions. Hierarchy can be created within the entity classes.

Entity types also enable you to create risks and controls for each entity without spending much time. For example, an organization can have multiple departments, such as finance, HR, or IT. All these departments can be
considered as entities and can be grouped under the entity type called Departments.  
You can create an entity type by associating it with the core business pillar such as Technologies or Facilities as shown in the following example.Figure 2. Sample configuration for an entity type

## Entity tiers {#what-is-an-entity__section_dwm_s33_qqb}

When you create entity tiers, you apply a level or hierarchy to the entity classes. This level applies to all the entities in those entity classes. Entity tiers enable you to select and view the status of the most critical items in the business as shown in the following example.Figure 3. List view for an entity tier

