--- sourceDocument: Australia ServiceNow AI Platform Capabilities sourceDocumentLink: https://www.servicenow.com/docs/r/australia/servicenow-platform Release : - australia ft:locale : - en-US ft:publication_title : - Australia ServiceNow AI Platform Capabilities ft:clusterId : - platcap bundleId : - platcap workflow : - Platform --- # Approval with e-signature # Approval with e-signature {#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 Approval with e-signature The Approval with e-signature feature in ServiceNow enables users to approve or reject records by re-entering their login credentials, ensuring compliance with Title 21 Code of Federal Regulations (CFR) Part 11 electronic signature requirements. This capability provides a secure and auditable way to validate approvals by capturing the signer's printed name, timestamp, and signature meaning (approval or rejection), all stored within the record's activity stream and audit history. Show full answer Show less ## Key Features * **Compliance Support:** Validated for Title 21 CFR Part 11 to meet electronic signature regulations. * **Approval Authentication:** Approvers must enter their credentials again to confirm approval or rejection; failed authentication prevents changes. * **Supported Tables:** By default, supports Change Request \[changerequest\] and Standard Change Proposal \[stdchangeproposal\] tables, with options to add or remove tables requiring e-signature approvals. * **Approval Options:** Approvals can be made via context menu options, UI actions, or by changing the record's state, each triggering an authentication dialog. * **User Credential Sources:** Supports local user records and remote identity providers via Multi-Provider Single Sign-On (SSO) integration with SAML 2.0. * **Audit Trail:** Each approval is recorded as a field change in the Approval record's activity stream for full traceability. * **Plugin Activation:** The Approval with e-signature plugin (com.glide.esignatureapprovals) must be activated to enable this functionality, with options to customize supported approval tables and authentication methods. ## Practical Application for ServiceNow Customers ServiceNow customers can leverage this feature to enforce stronger approval controls that comply with regulatory requirements, especially in environments requiring validated electronic signatures such as healthcare or pharmaceuticals. By requiring re-authentication for approvals, organizations reduce the risk of unauthorized approvals and increase accountability. Customers should ensure user credential sources are properly configured, either locally or via SSO, before enabling the plugin. The detailed audit trail helps maintain compliance and facilitates easier audits. ## Next Steps * Activate the Approval with e-signature plugin to enable e-signature-based approvals. * Configure approval tables as needed to control which tables require e-signatures. * Set up user authentication sources, either local users or SSO integrations, before enabling e-signature approvals. * Train approvers to enter credentials during approval to comply with e-signature requirements. * Use the audit and activity streams to monitor and review approval history for compliance verification. Approve or reject an approval record by re-entering your login credentials. See the history of an approval from its activity stream or its audit history. ## Support for Title 21 Code of Federal Regulations (CFR) Part 11 {#approval-with-e-signature__section_xtq_tkj_4xb} The Approval with e-signature plug-in is validated for Title 21 CFR Part 11 electronic signature requirements. This plug-in is required for compliance to 21 CFR Part 11. Each time someone approves a record, the system stores this information. * The printed name of the signer * The date and time when the signature was made * The meaning of the signature (approval or rejection) {#approval-with-e-signature__ul_pbk_blj_4xb} This information is stored as part of the activity stream and audit history of the record. ## Approval tables {#approval-with-e-signature__section_ngl_vy3_4xb} By default, Approval with e-signature supports these tables. * Change Request \[change_request\] * Standard Change Proposal \[std_change_proposal\] {#approval-with-e-signature__ul_q12_qp3_4xb} When you add an approval table, any approval for the table needs an e-signature authorization. See [Select an approval table](https://www.servicenow.com/docs/yYBRNnfCjndkkfOZN6zsnA "By default, activating the Approval with E-signature plugin enables e-signature for all tables for which an approval exists.") to add or remove a table from supporting Approval with e-signature. ## Approver Authentication dialog {#approval-with-e-signature__section_yjf_51j_4xb} Approvers must enter their user credentials to change the approval state. If the credentials fail, then the approval remains unchanged. The system checks the user credentials against local user records or an active single sign-on integration. ![Dialog to enter user credentials]() ## Approval History {#approval-with-e-signature__section_f3g_lqj_4xb} Each Approval \[sysapprover_approver\] record has an activity stream that tracks changes to it. Approvals made by e-signature are stored as field changes. Figure 1. Example activity stream ## Available approval options {#approval-with-e-signature__section_mw1_qx3_4xb} The Change Request \[change_request\] table provides these approval options. List options : The Change Request table provides context menu options to approve or reject records. When someone selects either the Approve or Reject context menu option, the system displays the Approver Authentication confirmation dialog. UI actions : The Change Request form provides UI actions to approve or reject a record. When someone selects either the Approve or Reject UI action, the system displays the Approver Authentication confirmation dialog. Change record state : The Change Request table provides a State field to approve or reject a record. When someone selects either the Approved or Rejected state, the system displays the Approver Authentication confirmation dialog. ## User credential sources {#approval-with-e-signature__section_wvk_mbj_4xb} Approval with e-signature supports these types of user credential sources. * A set of local User \[sys_user\] records. * A remote identity provider service accessed by the Multi-Provider Single Sign-On (SSO) integration. {#approval-with-e-signature__ul_jz2_zcj_4xb} User credentials must be set up before enabling Approvals with e-signature. See [Creating users](https://www.servicenow.com/docs/access?context=ua-creating-users&version=australia&pubname=australia-platform-administration&ft:locale=en-US) to create local User records. See [Multi-Provider single sign-on (SSO)](https://www.servicenow.com/docs/access?context=c_MultipleProviderSingleSignOn&version=australia&pubname=australia-platform-security&ft:locale=en-US) to create an integration to a Security Assertion Markup Language (SAML) 2.0 identity provider. * **[Activate Approval with e-Signature plugin](https://www.servicenow.com/docs/dHeHSx1v_V~_hBDbRiCv0Q)** The Approval with e-Signature plugin (com.glide.e_signature_approvals) allows users to approve requests by re-entering their login credentials. * **[De-activate e-signatures](https://www.servicenow.com/docs/98tXoYVUOCqlLGHrDGkiqw)** Use this procedure to de-activate e-signatures. * **[Select an approval table](https://www.servicenow.com/docs/yYBRNnfCjndkkfOZN6zsnA)** By default, activating the Approval with E-signature plugin enables e-signature for all tables for which an approval exists. * **[Set up an approval from a local database](https://www.servicenow.com/docs/v7fyuKJ3RujB4CEymCSkKw)** Enable users to authorize e-signature approvals using local database credentials. * **[Use Multi-Provider SSO to set up an SSO approval for a SAML 2.0 authentication](https://www.servicenow.com/docs/Bf6IrXi2H7Kde7NE6EPQsA)** An SSO approval with e-signature requires configuration on the SAML IdP and the ServiceNow instance. * **[Installed with approval with e-signature](https://www.servicenow.com/docs/jWBnd3AhCanIBnXZEW7MBw)** Installing approval with e-signature installs certain properties.