Falaah Falaah AI

Signatures

Built-in acknowledgments for internal documents are available today, with typed-name, timestamp, and IP audit trail. Legally binding e-signatures are coming.

Status: Not available yet

Legally binding electronic signatures (envelope-style: contracts, offer letters, NDAs) are on the Muin roadmap but are not available yet. We are choosing the right vendor partnership for the long term and will turn the feature on for paying customers when it ships.

In the meantime, built-in acknowledgments are available today for internal documents that need a recorded receipt: policy attestations, handbook acknowledgments, and other web-checkbox-style sign-off where a typed-name + timestamp + IP record is sufficient.

What’s available today

  • Built-in acknowledgments: type-your-name consent capture with timestamp + IP + user-agent audit trail. Free on every plan, unlimited usage. Used today for the Compliance Policy Hub attestation flow.
  • Document records: every acknowledged document is stored with full audit history and is exportable to PDF.

What’s coming

  • Legally binding e-signatures: PKI-based digital signatures with audit certificates, ESIGN Act and eIDAS compliance, tamper-evident PDF seals, embedded signing experience for contracts, offer letters, and NDAs.
  • Signature templates: save and reuse signature packages for common document types.
  • Bulk send: send the same document to many people at once.

The Signature activity screen

The admin screen exists in the app, at Administration → Signature activity (/admin/esignatures), ready for the day the feature is switched on. Owners and admins only.

Because e-signatures are turned off platform-wide today, the screen reads E-Signatures are not enabled for your organization with “Signature activity will appear here once e-signatures are switched on for this organization.” That is the expected state, not a fault with your account.

When the feature does ship, the screen has five tabs:

Tab What it shows
Signatures Every signature request in your organization, filterable by status (Sent, Partially Signed, Completed, Declined, Voided) and by type, with Export CSV
Audit Trail A chronological record of every signature event: who signed, declined or voided, and when
Usage Envelope consumption, add-on usage and any overage charges for the current billing period, against your Plan Usage
Metrics Completion Rate (target above 85%), Avg Completion (target under 72 hours) and Overage Revenue
Field Templates Company-wide field templates that pre-configure signature placement for common document types

Need it sooner?

If your organization has an immediate need for legally binding e-signatures, contact us: we’ll prioritize the rollout and notify you when it ships.

When it goes wrong

What you see What to do
“E-Signatures are not enabled for your organization” Expected today. The feature is off platform-wide while the vendor partnership is settled.
“Failed to load signature data. This is not an empty result: try again.” Reload. Muin is telling you it could not read the data, rather than showing you a false zero.
“No signatures yet” The feature is on for you and nothing has been sent. Not an error.
“Approaching plan limit: consider upgrading or managing usage.” Check the Usage tab for envelopes consumed, and either reduce usage or move plan.
Someone needs a signature today Use built-in acknowledgments for internal sign-off, as described above.