--- sourceDocument: Yokohama Governance, Risk, and Compliance sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/governance-risk-compliance Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Entity Based Access # Entity Based Access {#ariaid-title1} * Release version: Yokohama * * Updated July 31, 2025 * * ![](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 Entity Based Access The Entity Based Access (EBA) application, introduced in the Yokohama release, enables ServiceNow customers to enforce granular, entity-centric data segregation and access control. Unlike previous role-only based restrictions, EBA allows administrators to map users or user groups to specific entities, restricting access to records such as risks, controls, and issues by geographic or functional boundaries. This ensures users only access data relevant to their assigned entities, enhancing security and compliance. Show full answer Show less Administrators configure access by associating users or groups with entities or entity-related fields, minimizing unnecessary data exposure. Configuration is managed through the Entity Based Access Configurations module within the instance. ## Key Features * **Granular Access Control:** Enables detailed permissions tied to entities, including their hierarchical downstream records. * **Flexible Configurations:** Supports entity hierarchies, entity classes, and entity types to tailor access across groups of entities. * **Bulk Access Updates:** Allows gradual, selective application of access restrictions to large sets of records to avoid operational disruptions. * **Dynamic User Access:** Access is dynamically granted based on user or user group fields within entities, ensuring up-to-date permissions without manual intervention. * **Automated Access Rules:** Entity-based record access rules automatically enforce restrictions on new or modified records, maintaining consistent access controls. * **Deactivation Support:** Deactivating EBA disables configurations and automates record-level access evaluation to streamline administration. ## Important Considerations * EBA cannot be used simultaneously with User Hierarchy Access or User Group Access features. * Confidential users retain access to confidential records regardless of EBA configurations. * Performance and custom table usage limitations exist; customers should review relevant knowledge base articles for detailed guidance. ## Practical Use and Administration ServiceNow customers can use EBA to enforce entity-specific data access policies, particularly useful in regulated environments or multi-region organizations. The Entity Based Access record update utility assists in applying access changes across large datasets efficiently. Users with appropriate roles can manage and update EBA configurations and apply bulk updates. The application must be installed from the ServiceNow Store, followed by property setup in the instance. ## Supported Scenarios EBA is particularly effective for controlling access to Governance, Risk, and Compliance (GRC) tables and other supported objects, ensuring users see only records pertinent to their entity assignments. The Entity Based Access (EBA) application enables you to segregate data on the records that are based on entities. Entity-based access administrators can use this tool to set up secure, controlled access to various objects. ## Entity Based Access overview {#entity-based-access__section_kln_mmw_jfc} Before the Yokohama release, user restrictions were based only on their roles within the system without consideration for their geographical locations or specific functions. Access to objects like risks, controls, and issues was broadly managed. For example, a risk manager in North America had access to risk records across all regions, not just their own. From the Yokohama release onwards, Entity Based Access facilitates object access via entities. You can map entities to specific users or user groups, enabling you with a granular level of access control. With Entity Based Access, you can segregate data and manage access to help ensure that users can only access permitted data through entity-based access. Your administrators can grant access to an entity's related records. They can add users or user groups for access. Access can also be granted through entity user fields or entity user group fields, minimizing the risk of unnecessary data exposure. To use the Entity Based Access configuration, navigate to Entity Based Access Configurations in an instance. ## Key features of Entity Based Access {#entity-based-access__section_t14_hw3_qbc} Key features of the Entity Based Access configuration include: * Detailed control over access to various objects via entities within the system. * Versatile configuration options. For example, you can configure Entity Based Access within an entity hierarchy to restrict access to the entity and its downstream related records or across a group of entities by using an entity class or entity type. With bulk access update configurations, you can apply access restrictions selectively to scoped records. You can implement access restrictions gradually to help ensure smooth adoption without operational disruptions. * Access that is provided by including specific user field or user group fields in the entity-based access configuration. Users who are part of the configuration get dynamic access to the records. {#entity-based-access__ul_d5l_tmn_bcc} ## Key points to note about Entity Based Access {#entity-based-access__section_qdh_jts_z2c} Entity Based Access restricts access to records to users based on the configuration as shown in the following diagram: Figure 1. Entity-based access security flow The details about the entity-based access security flow are: * If User Hierarchy Access or User Group Access is enabled, you can't use Entity Based Access. * Confidential users can continue to access the confidential records whether they're or not part of the entity-based access configuration. {#entity-based-access__ul_sjs_mts_z2c} Important: * For information about the performance limitations, see [KB2069935](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2069935). * For information on how to use Entity Based Access on custom tables, see the steps in [KB1646304](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1646304). * For information about the limitations of Entity Based Access, see [https://support.servicenow.com/kb?id=kb_article_view\&sysparm_article=KB2054513](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2054513). {#entity-based-access__ul_cn3_3z1_cfc} * **[Sample use case scenarios](https://servicenow-prod.fluidtopics.net/3JcIC8Rf1v9SYvLZr0U6HA)** Use case scenarios offer a clear and comprehensive explanation of why you would use the Entity Based Access application. * **[User roles for Entity Based Access](https://servicenow-prod.fluidtopics.net/k5OwLmAUSwvpV0Gbs5xyrg)** Users with specific user roles have access to read or update the Entity Based Access configuration or the bulk access update configuration. * **[Entity based record access update utility](https://servicenow-prod.fluidtopics.net/wgFb10os86uLc_YXYVaS1w)** The entity based record access update utility is a guided assistance, designed to simplify the application of enabling or disabling access restrictions across large volumes of records. * **[Entity-based record access rules](https://servicenow-prod.fluidtopics.net/qsHJNayUeiKe4u3dHNVxag)** The entity-based record access rules let admins apply restrictions automatically to new and changed records. This configuration ensures that access settings stay enforced. No manual updates are needed when records are created, modified, or when users are added to user fields or user group fields. * **[Deactivating entity-based access configuration](https://servicenow-prod.fluidtopics.net/bGBilWKGA0N6Orpnbuglhg)** Deactivating entity-based access (EBA) not only disables the configuration but also streamlines admin workflows by automating record-level access evaluation. * **[Configuring Entity Based Access](https://servicenow-prod.fluidtopics.net/e6HZhF~DcAjmxJpWuK6nQA)** Configure the Entity Based Access application by installing it from the ServiceNow Store and by setting up Entity Based Access properties in the instance. * **[Managing Entity Based Access](https://servicenow-prod.fluidtopics.net/UDzGz5g_l5OrKGT8Ht_t7w)** You can manage access to the objects or record types in a system by using the Entity Based Access application. You can restrict access by using an entity, entity class, or entity type configuration. * **[Entity Based Access reference](https://servicenow-prod.fluidtopics.net/TS5blVW5PH7Tm_yiyVfCjg)** Entity-based access restriction can be applied on some GRC tables.