---
sourceDocument: Australia Workflow Data Fabric
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Workflow Data Fabric

ft:clusterId :

    - crint

bundleId :

    - crint

workflow :

    - Creator


---

# Using the Personal Authentication dashboard

# Using the Personal Authentication dashboard {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 Using the Personal Authentication dashboard

The Personal Authentication dashboard in ServiceNow provides a centralized, user-friendly interface for managing your personal credentials used in third-party integrations via Integration Hub.
It allows individual users to authenticate, revoke, and renew their personal authentication tokens without sharing superuser credentials, enhancing security and simplifying access management.
This feature requires an Integration Hub subscription.
Show full answer Show less  

## Dashboard Structure and Functionality

The dashboard consists of two main sections:

* **My Integrations:** Displays integrations currently authenticated with valid tokens. Each integration card allows you to revoke or renew authentication. Revoking invalidates tokens and moves the integration to the available section, while renewing refreshes tokens and extends expiration.
* **Integrations I can use:** Lists integrations available for authentication but not yet authenticated. You can authenticate these integrations to move them to the My Integrations section.

Authentication and renewal actions open a pop-up window. For ServiceNow integrations, you provide Username and Password to obtain an OAuth token. For other integrations, the OAuth credential page specific to the application is displayed.

## Setup and Configuration

If you are already using personal authentication credentials, enable the dashboard by installing the **Personal Authentication \[com.snc.snihubpersonalauth\]** plugin. Access the dashboard under **All \> IntegrationHub \> Personal Authentication \> Personal Integrations**. The dashboard reflects Connection \& Credential Aliases configured with the personal integration type and organizes them based on token validity.

If you are not yet using personal authentication credentials, create a Connection \& Credential Alias with an OAuth 2.0 credential and Integration Type set to Personal to enable personal authentication.

## Token Revocation

Revoking authentication removes all active tokens related to the user's session within the instance. For enhanced security, you can configure the OAuth Server's token revocation endpoint in the Application Registries form to enable token revocation at the OAuth Server level.

## Access Requirements

Users must have the **snpersonalauth.personalauthuser** role to access and use the Personal Authentication dashboard.  
Use your personal credentials to connect to third-party integrations. View, authenticate, revoke, and renew your personal authentications through a simplified, consolidated interface.

The Personal Authentication dashboard provides a streamlined way to manage your personal authentication integrations. With personal authentication, multiple users can use Integration Hub without needing to share superuser credentials. It also enhances security by removing the need to manage ACLs for third-party systems.

This feature requires an Integration Hub subscription. For more information, see [Legal schedules - IntegrationHub overview](https://www.servicenow.com/content/dam/servicenow-assets/public/en-us/doc-type/legal/snc-addendum-integrationhub.pdf).

## Dashboard overview {#personal-auth-dashboard__section_htc_jfx_lbc}

The Personal Authentication dashboard has two main sections.

* The My Integrations section at the top of the page, which shows your authenticated integrations.
* The Integrations I can use section at the bottom of the page, which shows the integrations available to you.
{#personal-auth-dashboard__ul_vfy_mt1_4bc}  
Figure 1. Personal Authentication dashboard  

My Integrations section

:   Displays authenticated integrations. Each integration has its own card. From the card, you can Revoke or Renew the authentication.

    When you revoke an authentication, you revoke any relevant access or refresh tokens for the personal authentication credential associated with the integration. Revoking invalidates the existing authentication. You can
    reauthenticate later to reestablish the connection. Once the authentication is revoked, the integration card moves to the Integrations I can use section of the dashboard.  
    Renewing an authentication renews the associated token and updates the expiration date. To renew, select the Renew button on the integrations card. This button opens a pop-up window where you can reauthenticate the credential. The contents of the pop-up window depend on the integration.

    * For ServiceNow integrations, the pop-up window has fields where you can enter the Username and Password for the credential, then select Get OAuth Token.
    * For all other integrations, the pop-up window displays your OAuth credential page for that application.
    {#personal-auth-dashboard__ul_gb2_ppp_sbc}

Integrations I can use section

:   Displays the integrations that are available but not authenticated. To authenticate, select the Authenticate button on the integration card. Authenticating opens the same pop-up window that opens when
    you Renew an integration: For ServiceNow integrations, the pop-up window has the Username, Password, and Get OAuth Token buttons. For all other integrations, the
    pop-up window displays your OAuth credential page for that application.

    Once the credential is authenticated, the integration card moves to the My Integrations section at the top of the dashboard.

## Required dashboard setup {#personal-auth-dashboard__section_w3g_kv1_4bc}

If you're already using the personal authentication credential type, you can upgrade to the dashboard by installing the Personal Authentication \[com.snc.sn_ihub_personal_auth\] plugin. After installing the plugin, navigate to AllIntegrationHubPersonal AuthenticationPersonal Integrations to see the dashboard.  
The integrations on the dashboard all come from the Connection \& Credential Aliases \[sys_alias\] table. Any alias where the credential has a personal integration type is displayed on the dashboard, according to the following guidelines.

* If the credential currently has a valid token, it's listed in the My Integrations section of the dashboard.
* If the credential doesn't currently have a valid token, it's listed in the Integrations I can use section of the dashboard.
{#personal-auth-dashboard__ul_xz2_tgc_qbc}

If you're not already using the personal authentication credential type, you can configure one by creating a Connection \& Credential Alias that uses an OAuth 2.0 credential with the Integration Type of
Personal. For more details and instructions, see [Create a Connection \& Credential alias](https://www.servicenow.com/docs/access?context=connection-alias&version=australia&pubname=australia-platform-security&ft:locale=en-US).

## Token revocation URL {#personal-auth-dashboard__section_dpl_5md_4bc}

Revoking an authentication revokes all the related active tokens stored in the instance for the user that initiated the session. You can also enable token revocation on the OAuth Server by providing the server's token revocation
endpoint in the Token Revocation URL field.  
To enable authentication revocation at the OAuth Server, fill in the Token Revocation URL field in the Application Registries form for the integration's OAuth Provider. To fill in this field, follow these steps.

1. Navigate to AllSystem OAuthApplication Registry.
2. Select the form for the appropriate OAuth Provider from the Application Registries \[oauth_entity\] table.
3. In the Token Revocation URL field, enter the OAuth Server's token revocation endpoint.
{#personal-auth-dashboard__ol_w4z_bhc_qbc}

## Roles {#personal-auth-dashboard__id_pw4_y5r_rbc}

The Personal Authentication dashboard requires the sn_personal_auth.personal_auth_user role.

*[\>]: and then


