---
sourceDocument: Brazil Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Approval with e-signature

# Approval with e-signature {#ariaid-title1}

Release version: Brazil  
Updated September 10, 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 plug-in enables ServiceNow customers to approve or reject records by re-entering their login credentials, ensuring secure and compliant approval processes.
This functionality supports Title 21 Code of Federal Regulations (CFR) Part 11, which governs electronic signatures for FDA-regulated industries.
The plug-in records critical signature details such as the signer's printed name, the date and time of the signature, and the meaning of the signature (approval or rejection).
All this information is stored in the activity stream and audit history of the approved record for traceability.
Show full answer Show less  

## Key Features

* **Compliance:** Validated for 21 CFR Part 11 electronic signature requirements, making it essential for regulated environments.
* **Supported Tables:** By default, it supports Change Request \[changerequest\] and Standard Change Proposal \[stdchangeproposal\] tables. Customers can add other approval tables to require e-signature authorization for approvals.
* **Approver Authentication:** Approvers must authenticate by entering their credentials via a confirmation dialog before approval or rejection actions take effect. Failed authentication prevents state changes.
* **Approval History:** Each approval record maintains an activity stream that logs all changes, capturing e-signature approvals as field changes for auditability.
* **Approval Options:** Approvals can be performed through context menu options, UI actions, or by changing the record's State field with all methods invoking the authentication dialog.
* **User Credential Sources:** Supports local user records and remote identity providers through Multi-Provider Single Sign-On (SSO) integration, including SAML 2.0 providers. Proper credential setup is required prior to enabling the plug-in.

## Practical Benefits

ServiceNow customers can confidently implement secure and compliant approval workflows that meet regulatory requirements for electronic signatures. This capability ensures that only authenticated users can approve or reject records and that all approval actions are transparently tracked and auditable. The flexible integration with local users and SSO providers supports diverse enterprise authentication environments.  
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/k28NvGDo6Zwq9RdycKN2~g "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=brazil&pubname=brazil-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=brazil&pubname=brazil-platform-security&ft:locale=en-US) to create an integration to a Security Assertion Markup Language (SAML) 2.0 identity provider.

