---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

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}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

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/iv3lb8jEEgCWD0kh1h6Asg "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.  
Abbildung : 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://servicenow-prod.fluidtopics.net/zdLriVCPY0qP1FffqlbzuQ)**   
  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://servicenow-prod.fluidtopics.net/RcFly1qaxO82p~E_BATsTw)**   
  Use this procedure to de-activate e-signatures.
* **[Select an approval table](https://servicenow-prod.fluidtopics.net/iv3lb8jEEgCWD0kh1h6Asg)**   
  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://servicenow-prod.fluidtopics.net/sQ~ZdxCANtgrc1EEXeB2SA)**   
  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://servicenow-prod.fluidtopics.net/CsppMIHdsaBKnflta~vF~Q)**   
  An SSO approval with e-signature requires configuration on the SAML IdP and the ServiceNow instance.
* **[Installed with approval with e-signature](https://servicenow-prod.fluidtopics.net/Qr09hLr0mDAnv~AFt7Apxw)**   
  Installing approval with e-signature installs certain properties.