---
sourceDocument: Australia Platform security
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/platform-security

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Exploring Federated ID

# Exploring Federated ID {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The ServiceNow® Identity system deduplicates users across multiple instances using their User ID and email, and assigns each resolved user a unique Federated ID for consistent identification.

With Federated ID, you can accurately calculate the number of unique users across instances, which is useful for licensing and user management. For more information, see [Federated ID](https://www.servicenow.com/docs/vr5Hv3v2ZAQdiSV9lU_o8w "The ServiceNow Identity system deduplicates users across multiple instances using their User ID and email, and assigns each resolved user a unique Federated ID for consistent identification.").  
Note:  
User name is required for generating Federated IDs.

With the user's User ID and Email (default setting) to identify and match users across instances, ServiceNow® generates a unique Federated ID with a hashing function and stores it in the sys_user table.  
Note:  
* User ID is required for generating Federated IDs. If the user name is null or empty, then the Federated ID is null.
* User ID and Email are used to generate Federated IDs by default. To configure the fields used for generating Federated IDs based on your requirements, see [Update ID fields](https://www.servicenow.com/docs/bUd5zNBaVgT1SvFU~bp1TA "To generate new Federated IDs, you can either use the existing user resolution search criteria or update the criteria before regeneration."). You must have the Iamsync_admin role to update the configuration.
* If multiple users share the same user name and email, the system generates a Federated ID for only one of the users.
{#federated-id__ul_ev2_yt1_5xb}

After upgrading to the Australia release, the Federated ID Generation (com.glide.identity.globalid) plugin is auto-installed on all instances. After the plugin is installed, the schema changes are as
follows:

* A column federated_id in the sys_user table is created.
* A table - iamsync_type is auto-populated with the default configuration for the sys_user table.

{#federated-id__ul_h4q_ynn_3xb}

Federated ID is only supported for the sys_user table and all the tables that extend the sys_user table.