---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Entity classes in GRC

# Entity classes in GRC {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Entity classes are used to tag your entities and to provide a complete view of the risk
status in your organization.

Entity classes are tags. After tagging the entities, you can gather data based on entity tags.
To understand the concept of entity classes, consider the following example. Assume that the
Chief Risk Officer (CRO) of your organization wants to see the risk status of all the business
applications across all the divisions in the business. As a risk analyst, you can show the CRO
the dashboard for the Business Applications entity class.

For more information on how to create an entity class, see [Create entity class using the GRC: Workbench](https://servicenow-prod.fluidtopics.net/y3NdvMC1VD0kwGzqf_fqag "GRC managers create entity classes representing the types of things that are part of the dependency model. Reports can be filtered to define relationships between the different enity classes. An entity class defines what a entity actually is.").
**Related concepts**   

* [Entity tiers in GRC](https://servicenow-prod.fluidtopics.net/YOUJozMsa45SbonbB9fnxg "By creating entity tiers, you can prioritize the entity classes.")