Send documents for signature without leaving your workspace

Prepare PDFs, add recipients, place signature fields, send secure signing links, and keep every status change attached to the same Figena organization workspace.

A complete signing flow for operating teams

Built around the workflow that already exists in Figena: document preparation, routed recipients, internal inboxes, public signing links, completed files, and event history.

PDF document setup

Upload a source PDF through the signing workspace, name the envelope, set the message, and keep drafts separate from sent documents.

Recipients and routing

Add internal workspace members or external recipients, assign signer, approver, or CC roles, and control routing order.

Field placement

Place signature, typed signature, initials, full name, date, email, text, and checkbox fields directly on the PDF.

Secure send actions

Send, resend, remind, cancel, and download documents from one dashboard while status badges stay visible.

Signer inbox

Internal recipients can act from their own inbox with action-required, waiting, completed, declined, expired, and canceled states.

Events and evidence

View document events, signed field submissions, completion timestamps, and the completed PDF once the workflow is done.

Designed around the real document lifecycle

E-Signature gives operators a practical signing system instead of a detached upload-and-send tool. Every envelope stays connected to recipients, fields, status, downloads, and event history.

Turn a PDF into a signable envelope

Start from a source PDF, add message details and expiration timing, then place fields for the right recipient before the document is sent.

Draft before send

Managers can edit title, message, expiration, recipients, and fields while the document is still a draft.

Field-level control

Required fields are positioned by page with dimensions and recipient ownership, so signers see exactly what they need to complete.

Route work to internal and external signers

Recipients can be workspace members or external contacts. Roles and routing order help separate signers, approvers, and people who only need a copy.

Internal inbox

Workspace members get an inbox view that separates action-required work from waiting and completed documents.

Public access

External recipients use secure public signing links backed by token-based access and public request limits.

Give recipients a focused completion surface

The signing view shows the source PDF alongside required fields. Recipients can draw or type a signature, fill values, submit, or decline with a reason.

Field validation

The submission flow collects values for each assigned field and updates recipient and document status.

Clear state handling

Completed, declined, canceled, expired, and waiting states are shown directly in the signing experience.

Keep the signed result and the operational trail together

Once signing is complete, teams can download the completed document and review the event timeline attached to the envelope.

Completed PDF

Download actions return the available source or completed file based on the document state.

Event history

Document actions such as sending, viewing, signing, declining, canceling, reminding, and downloading are preserved as events.

From draft to completed document

The signing workflow is explicit, so teams can see where a document is and what needs to happen next.

Create the envelope

Upload the PDF, set the document title, message, expiration date, and recipients.

Place fields

Assign required fields to recipients and position them on the correct PDF page.

Send and track

Send the document, then monitor recipient status, reminders, resends, and inbox action states.

Complete and download

After all required recipients finish, download the completed file and review the event timeline.

Questions, answered

Does E-Signature support external signers?

Yes. External recipients can access the public signing flow through secure token links, while internal members can use the workspace inbox.

What field types are supported?

The current implementation supports signature, typed signature, initials, full name, date, email, text, and checkbox fields.

Can a manager cancel or resend a document?

Yes. The workspace supports send, resend, remind, cancel, download, and field management actions.

Can recipients decline?

Yes. Internal and public signing flows both include a decline action with an optional reason.

Is there an event history?

Yes. Documents expose event history for the actions performed across the envelope lifecycle.

Is this separate from Scheduling?

Yes. Scheduling handles team shifts and coverage. E-Signature handles document envelopes, recipients, signing fields, and completed files.

Bring document signing into the same workspace as the work

Use E-Signature for agreements, approvals, acknowledgements, and operational paperwork that needs a clear completion trail.

Get started Explore Scheduling