--- sourceDocument: Yokohama Build workflows sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Approval with e-signature # Approval with e-signature {#ariaid-title1} Release version: Yokohama Updated January 30, 2025 ![](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 enhances approval processes by requiring approvers to re-enter their login credentials to approve or reject records. This ensures compliance with Title 21 Code of Federal Regulations (CFR) Part 11 for electronic signatures, making it essential for regulated environments. Each electronic approval captures the signer's printed name, timestamp, and the meaning of the signature (approval or rejection), which is stored securely as part of the record's activity stream and audit history. Show full answer Show less ## Key Features * **Compliance Support:** Validated for 21 CFR Part 11, ensuring regulatory compliance for electronic signatures. * **Supported Approval Tables:** By default, supports approval on Change Request \[changerequest\] and Standard Change Proposal \[stdchangeproposal\] tables. Additional approval tables can be configured to require e-signature authorization. * **Approver Authentication:** Approvers must authenticate by entering user credentials through an approval confirmation dialog. Failed authentication prevents approval state changes. * **Approval History Tracking:** All approvals with e-signature are recorded as field changes in the activity stream of Approval \[sysapproverapprover\] records, providing a transparent audit trail. * **Flexible Approval Options:** Approvals or rejections can be performed via context menu options, UI actions, or by changing the state field on the Change Request table, each triggering credential re-entry. * **User Credential Sources:** Supports local user records or remote identity providers through Multi-Provider Single Sign-On (SSO) integration, allowing flexibility in authentication methods. ## Practical Benefits for ServiceNow Customers This capability empowers organizations to securely enforce electronic approvals with verifiable signatures, fulfilling compliance mandates and improving accountability. Customers can expect a seamless integration of e-signature prompts within their existing approval workflows, with detailed audit trails for compliance reporting and investigation. The support for multiple authentication sources allows adaptation to diverse security environments. ## Next Steps * Ensure user credentials are properly configured either locally or via SSO before enabling the Approval with e-signature plug-in. * Configure additional approval tables if your business processes require e-signature authorization beyond the default tables. * Train approvers on the authentication process to avoid approval delays caused by failed credential entries. 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/ucmpFHGE1Qnjy2MMHZoT~Q "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=yokohama&pubname=yokohama-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=yokohama&pubname=yokohama-platform-security&ft:locale=en-US) to create an integration to a Security Assertion Markup Language (SAML) 2.0 identity provider.