Skip to main content

E-Signature Configuration

# E Signature
Last updated: 04/14/2026

Understand how to access Signature settings and what is configurable in the current study state.

Overview

The Signature configuration page is available from the study-level app settings area.

In this environment, the page displays informational messages and does not expose editable settings.

note

Live UI messages shown on the page:

  • "To set it up, please change the status of Study to Design"
  • "There is no configuration for this application."

These messages indicate that Signature setup is controlled by study status and application availability rather than a dedicated settings form.


Access Path

Step 1: Open My Page

Log in and open My Page.

My Page

Step 2: Open Study Home

In Current study, click Go to Study Home.

Study home with Installed Apps

Step 3: Open Signature configuration page

From study home, open the app configuration route for Signature.

Open Signature configuration

Step 4: Review current configuration behavior

The page currently shows a status note and no editable controls.

Signature configuration status note

No configurable fields on Signature page


What Can Be Configured Here?

Based on the live page in this study:

  • No form fields are available
  • No save/discard action buttons are shown
  • Configuration is effectively read-only/informational at this level

If your environment has additional Signature controls, document them according to your tenant configuration and study status policy.


Relation to Signing Workflow

Even when no settings are available on this page, users can still work in the operational Signature workspace (top navigation Signature) to sign eligible records.

For the full signing flow, see Overview.


Access Requirements

Signature behavior depends on user role, study status, and record eligibility.

  • Users must have permission to access Signature workspace actions
  • Sign actions require credential confirmation (username + password)
  • Signature actions are audit-trailed with timestamp and user identity