--- sourceDocument: Australia IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Notifications on tool credential expiration # Notifications on tool credential expiration {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](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 Notifications on Tool Credential Expiration ServiceNow DevOps Change Velocity sends notifications to tool users when tool credentials expire or are about to expire, helping prevent data loss by prompting timely credential updates. This functionality primarily targets users with thesndevops.toolownerorsndevops.adminroles. Show full answer Show less ## How Notifications Work * A **universal task** is created and assigned to users with the **sndevops.toolowner** role (who belong to any user group specified in the "Maintained by" field) and users with the **sndevops.admin** role. Notifications about this task are sent via the notification bell icon, email, and an open task on the workspace home page. * A **banner message** appears on the tool record for all users with access when credentials expire. * For GitHub tools using basic authentication, a **field message** is also displayed on the Credentials expiration field to proactively warn users before expiration. ## Timing and Configuration * The system checks for credential expiration every hour, with notifications sent within that interval after expiration. * Proactive notifications for GitHub tools with basic auth are sent based on a configurable property: **"Number of days before tool credential expiry to assign a universal task and notify"**, which defaults to 3 days. Setting this to 0 disables proactive notifications. * Notifications after expiry can be disabled by turning off the **"Assign a universal task and notify to update tool credentials when expired"** property. ## Practical Impact and Actions * Expired tool credentials cause the tool to disconnect, interrupting data flow. * Users notified with the appropriate roles can update credentials by selecting the **Update credentials** link in the notifications. * After updating credentials, users must reconnect the tool to resume data collection. This notification mechanism ensures that tool owners and administrators maintain valid credentials, minimizing downtime and data loss in DevOps integrations. Notifications are sent to tool users on expiration of tool credentials to alert them. Notifications are also sent proactively before the expiration of tool credentials for GitHub tools created with basic authentication. This enables tool users with the sn_devops.tool_owner or sn_devops.admin roles to update the tool credentials and prevent any loss of data. A universal task is created and assigned to users with the sn_devops.tool_owner role who are part of any user group specified in the Maintained by field, and any user with the sn_devops.admin role. They will be notified of the universal task through notification (in the bell icon), email, and an open task in the workspace home page. Notifications are also displayed in the tool record in the form of a banner message to any user with access to the tool when the tool credentials expire. But the credentials can be updated only by users with the sn_devops.tool_owner or sn_devops.admin role. The credentials expiration check happens in the system every one hour. If your tool credentials have expired, it might take a maximum of one hour for the system to send notifications. For GitHub tools created with basic auth, notifications are also sent proactively before the expiration of tool credentials. Apart from the universal task and banner notification, a field message is also displayed in the case of proactive expiration notifications. You can set the number of days before which expiration notifications must be sent in the Number of days before tool credential expiry to assign a universal task and notify (if applicable) property. By default, it is set to 3 days. To stop sending proactive notifications, select 0 as the value for this property. If you want to stop sending notifications for expired credentials after expiry, disable the Assign a universal task and notify to update tool credentials when expired property. For more information, see [DevOps Change Velocity properties](https://www.servicenow.com/docs/Cy67V7Lf9sOXU2beB3VARQ "Use these properties to configure settings in the DevOps Change Velocity application."). The following types of notifications are sent: Universal task : A universal task is created and notifications are sent to users with the sn_devops.tool_owner role who are part of any user group specified in the Maintained by field, and any user with the sn_devops.admin role. Banner message : A banner message is displayed on the tool record to all users with access to the tool record. Field message : A field message is displayed on the Credentials expiration field in the tool record for a GitHub tool created with basic auth. When the credentials of your tool expire, the tool gets disconnected. You can select the Update credentials link in the notifications, and update your tool credentials. After the credentials are updated, connect to the tool again to start receiving data. For information on updating tool credentials, see [Update third-party tool credentials in DevOps Change Velocity](https://www.servicenow.com/docs/W3H0I3eiOCLVglPK635qzA "If your tool credential has changed, you must update the credentials in your ServiceNow instance to avoid getting disconnected.").