> This page is for Harness. > For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.moveworks.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.moveworks.com/_mcp/server. # Configuring Entities in Moveworks Setup ## Entity Configuration Guide On the home screen of Entity Catalog, you can view two types of entities: **Custom Entities** and **Global Entities**. **Custom** **Entities**: Organization-specific software entities created and managed by admins. These typically represent internal applications, tools, or systems unique to your enterprise. E.g. ExpenseIQ, TimeOff, and EmployeeConnect. The **Custom Entities** tab provides the following information and actions: * **Entity Name** – Display name of the entity *(not editable after creation)* * **Canonical Name** – Unique system-generated identifier used internally * **Description** – Brief description of the software application * **Created By** – User who created the entity * **Last Updated By** – User who last modified the entity * **Created At** – Entity creation timestamp * **Last Updated At** – Most recent modification timestamp * **Available Actions** * **Search** – Search for existing entities * **Create New** – Create a new custom entity * **Edit** – Modify an existing custom entity **Global** **Entities**: Predefined software entities managed by Moveworks and available across all customer environments. Admins can override existing global entities if needed, but cannot create new ones. E.g. Salesforce, Zoom, and Figma. > **Note** > > **Note**: Admins cannot create new global entities, but they can override existing ones to customize entity behavior for their organization. * **Entity Name** – Display name of the entity *(not editable)* * **Canonical Name** – Unique internal identifier * **Description** – Brief description of the software application * **Available Actions** * **Search** – Search across available global entities * **Override Settings** – Customize an existing global entity for your organization ## Understanding Key Configurations The Entity Configuration screen allows admins to define how entities are identified, matched, and displayed within Moveworks. Below is a breakdown of the key configuration fields and their purpose. ![](https://files.readme.io/374e5dff1a5a4f584b6d4ce359a41a386345f690a4b30d21dcbf9def6ef796e2-entity_details_page_1.png)
Term Definition Example
Title (Not editable) Preferred entity name shown to users `Zoom`, `Figma`, `Loom`, `Notion`, and more
Canonical Name Moveworks ID ServiceNow Service Catalog → `servicenow_service_catalog` WebAssembly → `webassembly` Dolby.com → `dolby_com` Canonical name is snake case with spaces converted to ‘\_’ underscores
Description A brief description of the entity shown to users “Zoom unifies cloud video conferencing, simple online meetings, and cross platform group chat into one easy-to-use platform.”
Entity Type (Not editable) Classify entities according to different use cases Software Applications
Aliases Alternate names for an entity `zoom`, `zoom video`, & `zoom pro` would be the aliases for Zoom, the video conferencing software
Exact matching logic Matches a word or phrase exactly `zoom pro` would always match with zoom entity in EC
Fuzzy matching logic Match a word or phrase to within a certain edit distance `zooom` (intentional spelling mistake) would try to match with zoom entity in EC. By default, this option will be selected for aliases
Negative aliases Prevents matches against a word or phrase that would otherwise match `loom` & `moom` entities would be negative aliases for Zoom video conferencing software since those two are different apps with very similar names
> **Important Notes** > > 1. 1. The **Title** also serves as the entity’s primary alias and cannot be modified after the entity is created. > 2. 2. Currently, **Software Application** is the default and only supported entity type in Entity Catalog. > 3. 3. Canonical names are automatically standardized using lowercase snake_case formatting. \ ## **Create or Override Software Entities** Before creating a new software entity, first check whether the entity already exists in Moveworks Setup. Admins may want to override existing global entities when the entity already exists, but its behavior needs to be customized for organization-specific terminology, workflows, or naming conventions. For example, an admin may want the **Figma (a global entity) **entity to also recognize related terms such as: * FigJam * Figma design tool * Figma workspace * Design collaboration platform By overriding a global entity and configuring custom aliases or matching behavior, admins can improve entity recognition and ensure users are directed to the correct workflows and experiences. ### **Step 1: Search for Existing Entities** Search whether the software entity already exists via checking **Moveworks Setup** > **Access Software** > **Software Catalog** > **Software/Application Name config.** ### **Step 2A: Override an Existing Global Entity (If the Entity Already Exists)** If the entity is available under **Global Entities**, use the **Override Settings** option to customize the entity for your organization. Admins can override: * Descriptions * Positive Aliases * Matching behavior (Fuzzy/Exact) * Negative Aliases > **Note** > > **Note**: After a global entity is overridden, it will also appear in the **Custom Entities** section with a `Custom Override` tag, since the configuration is now customized for your organization. ### **Step 2B: Create a New Custom Entity (If the Entity Doesn't Already Exists)** 1. Confirm that the software entity is not already available in the search results or dropdown list. If the desired application is not found, create a new custom entity. ![](https://files.readme.io/e98cd11228fcfb5b40b84c100fc477475ea670f370b1c48a048238a08aac1041-image.png) 2. Navigate to **Entity Catalog **and click on **Create** **New **button ![](https://files.readme.io/f448b6fe27dd0c6a077085937ce40ee7ab79a93fd5e22c99fa12f86f667bc1f1-create_entity_1.png) 3) Fill in **all** required the fields | Field | Value | | ----------------- | --------------------------------------------------------------------------------------------------------------------------- | | Title | Zoom | | Short Description | Zoom unifies cloud video conferencing, simple online meetings, and cross platform group chat into one easy-to-use platform. | | Entity Type | Software Application (selected by default) | | Entity Aliases | `zoom`, `zoom video`, `zoom pro` | | Negative Aliases | `loom` | 4. Click on **Submit Button** to create the entity ## Modify Software Entities 1. Navigate to **Moveworks Setup** > **Entity Catalog** and Click on **Edit Button** 2. Edit the fields that you want to modify in Entity Details page * Edit Description, or * Add, update or remove Aliases, or change their matching logic, or * Add, update or remove Negative Aliases ![](https://files.readme.io/d60322363963da20c8d64cac803e6434b16e778be89a69e07ecf3b0dff7d7128-edit_entity_2.png) 3. Click on **Submit Button** ## Where to Utilize Software Entities? 1. Navigate to **Moveworks Setup** > **Access Software** > **Software Catalog** ![](https://files.readme.io/214d06adbab8a6336aa3b2cb5b165d9ec2fc37922af4af36a2a28bc0dbe16816-image.png) 2. Search for the entity in the **Software/Application Name** field ![](https://files.readme.io/25665189d2bea3e91cda83c4034e95a3a4e13b518137223ef2c3e8d434925866-image.png) 3. Setup the Software Provisioning for the Software or Application. For more information, read the guide on [Provision Management](/service-management/provision-management/overview)