--- sourceDocument: Australia Build workflows sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # 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 plug-in captures and securely stores vital signature information such as the signer's printed name, timestamp, and the meaning of the signature (approval or rejection). This data is maintained in the activity stream and audit history of the approved record, supporting regulatory and audit needs. Show full answer Show less ## Key Features * **Regulatory Compliance:** Validated for 21 CFR Part 11 to meet electronic signature standards. * **Supported Tables:** By default, supports Change Request \[changerequest\] and Standard Change Proposal \[stdchangeproposal\] tables. Administrators can add other approval tables to require e-signature authorization. * **Approver Authentication:** Approvers must authenticate by entering their user credentials to confirm approval or rejection. Failed authentication prevents state changes. * **Approval History Tracking:** Each approval record tracks changes in an activity stream, with e-signature approvals recorded as field changes, providing clear audit trails. * **Multiple Approval Methods:** Approvals can be performed via context menu options, form UI actions, or by changing the state field. All methods invoke the approver authentication dialog. * **Credential Sources:** Supports local user records and remote identity providers via Multi-Provider Single Sign-On (SSO) with SAML 2.0. User credentials must be configured prior to enabling e-signature approvals. ## Practical Benefits for ServiceNow Customers This feature enables customers to enforce strong authentication for approval actions, ensuring that only authorized users can approve or reject critical records. It enhances audit readiness by capturing detailed signature metadata and maintaining comprehensive approval histories. Compliance with 21 CFR Part 11 is simplified for regulated industries by integrating electronic signature validation directly within ServiceNow workflows. Customers can flexibly configure which tables require e-signature approvals and leverage existing identity management systems for seamless authentication. 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://servicenow-prod.fluidtopics.net/XY18oXc5FZEPSOw9Ay4k4Q "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.