Skip to main content
Document signatures is the ledger of every accepted document in your organization. It records which member accepted which document, when, how it was signed, and the version of the document at the time - evidence you can produce for compliance. A signature is the proof that a member accepted a required or optional document, captured when they sign through the member portal, the mobile app, the public signup wizard, a form on a tablet station, the check-in tablet, or a signing link you email from their profile. Owners and admins use the ledger to check and prove who has signed.

When to use it

The ledger answers “did this person sign, and what exactly did they agree to?” in one place. You can check it before someone trains and produce the evidence if an agreement is ever questioned. Typical uses:
  • Check a waiver before a high-risk session - before a member’s first climbing session or sparring class, open the Documents tab on their profile and confirm the waiver shows Signed, not Not signed.
  • Settle an onboarding dispute - open the signature to see the document version, typed name, and timestamp, and download the signed agreement as a PDF.
  • Keep an accurate record for kids’ programs - when a parent enrolls a child, the waiver sits on the child’s record with the parent recorded as the signer.

How signatures are created

Signatures land in the ledger from several flows:
  • Public signup wizard - The onboarding flow captures acceptances (including drawn signature, IP, and user agent) for the member and, where applicable, their children.
  • Member portal - Members sign outstanding required documents from their own portal.
  • Mobile app - Members can review and sign required documents from the 1club mobile app.
  • Check-in tablet - A member refused at self check-in because they owe a document required for entry signs it on the Check-in App after identifying with their full PIN or QR code.
  • Tablet station - New visitors sign as they fill in a form left open as a Tablet station.
  • Send for signature - From the Documents tab of a member’s profile, staff email the member a link to read and sign a document they owe. See Sending a document for signature.
The ledger can also show a Type of Physical for a paper acceptance. There is no screen in the admin for recording one by hand. A member is not asked to re-sign for cosmetic edits to a published document; a fresh acceptance is only recorded when a genuinely new signature is submitted. A repeat submission of the same document version on the same day is rejected to avoid duplicate rows.

The signatures list

Open Members, then pick Signatures in the three-dot overflow menu next to Add member (route /members/document-signatures). The menu entry is shown to staff who can read settings. The signable documents and the rules that require them are configured separately under Settings > Members > Waivers. The list shows the signatures on file, with these columns:
  • Document - The title of the signed document.
  • Contact - The member the signature belongs to. Click the name to jump to their profile.
  • Status - Signed, or Awaiting approval for a signature staff still have to check (see Signatures awaiting approval).
  • Signed Date - When the acceptance was recorded.
  • Type - Electronic (signed online) or Physical (a paper acceptance).
The ledger lists only documents someone has signed. To see which required documents a member still owes, open the Documents tab on their profile, where each one shows as Not signed. From the toolbar, Create Document starts a new document, and Documents and Waivers opens the documents and rules.

Signature detail

Click any row to open its detail page.
  • Signature Details - The document (a link to its content item), the signature type, and Signed Date, which lists every acceptance for that member and document with its timestamp. Because a document can be re-signed (for example after a new version), each acceptance is kept rather than overwritten.
  • Status - Signed, or one of the statuses below.
  • Document Version - The version of the document that was accepted, so you can prove what the member actually agreed to.
  • Typed name - The full name the member typed, shown when the document required typed-name acceptance.
  • Member - Contact card for the member the signature belongs to. For a child signed for by a parent, this is the child, not the parent who signed.
A signature that no longer counts shows why in Status:
  • Awaiting approval - the signer could not confirm their email or phone, so staff have to approve it first.
  • Withdrawn by the member - an optional document the member accepted and later declined.
  • Lapsed: signed by a guardian, now 18 or older - a parent signed it for a child who has since turned 18. The adult now owes their own signature.
  • Signature evidence - When present, a card with the drawn-signature image, the acceptance timestamp, the IP address, and the device / user agent.
The evidence card only appears when those fields were captured. Signatures collected by the signup wizard carry the drawn image, IP, and user agent; acceptances from older flows, typed-name-only acceptance, or a physical record entered by staff may show fewer fields, and the card is hidden when none are present.

Downloading the signed agreement

The Download button on a signature detail page produces the signed onboarding agreement as a PDF - the member’s details, household, the documents they accepted, and their signature, with an IP and device footer. The PDF is generated on demand and served behind your admin session; it is never stored at a public URL.

Signatures awaiting approval

A form can be set to Confirm the signer’s email or phone. Someone signing it without being signed in then gets a code to their email, WhatsApp, or phone. If no code reaches them, they can still finish, but the signature is filed as Awaiting approval. It does not count anywhere, for example toward a document required for entry, until staff approve it. To review one, open the member’s profile, go to the Documents tab, and use the row’s actions:
  • Approve signature - once you have checked who they are, for example with an ID. The signature then counts as the member’s own.
  • Discard signature - the member will need to sign again.
Approving and discarding need check-in create (front desk) or members update access. Held signatures also show in the org-wide ledger, but are approved from the profile.

Sending a document for signature

On the Documents tab of a member’s profile, a required document the member has not signed shows as Not signed. Its row action Send for signature emails the member a link to read and sign it, and you see who it was sent to. The link is valid for 30 days, and signing through it records an ordinary signature.
  • The member needs an email address. Without one the action is disabled with “Add an email address to send it.”
  • A link can’t be sent to a member under 18: a parent or guardian has to sign for them.
  • It needs check-in create (front desk) or members update access.

Typed-name acceptance

When a document rule has Require review and typed name switched on, the member must scroll through the whole document and type their full name before the accept button unlocks. That typed name is stored on the signature and shown as Typed name on the detail page, alongside the timestamp and any captured evidence. This is the strongest self-serve acceptance you can require and is the recommended setting for liability waivers.

Guardian signing for children

When a household enrolls a child (for example a parent registering a child for a kids’ program), the guardian accepts the child’s documents on their behalf during the signup wizard. In the ledger:
  • The subject of the signature is the child - the row belongs to the child’s contact and appears under their profile.
  • The signer is the guardian - the acceptance is attributed to the adult who actually completed the wizard.
This lets you route a minor’s waiver to the Child household role (see Documents and waivers) while keeping an accurate record that a responsible adult signed it. The guardian only signs documents they explicitly accepted in the wizard - the child’s required documents are presented to the guardian, and each accepted one is recorded as a separate signature for the child. A guardian’s signature stops counting when the child turns 18. It then shows as Lapsed: signed by a guardian, now 18 or older, and the new adult is asked to sign for themselves.

Tips and best practices

  • Use typed-name acceptance for waivers. It forces the member to scroll and type their name, and the typed name is preserved on the signature as evidence.
  • Check status before high-risk activities. A Not signed row on a member’s Documents tab means a required document is unsigned - useful to confirm before a first climbing session, sparring class, or contact-sport match.
  • Download the agreement for your records when onboarding disputes arise; the PDF captures the exact documents and signature.
  • Attribute minors correctly. For children, expect the signature to sit on the child’s record with the guardian as signer - that is the intended model, not a data error.

Troubleshooting

  • Documents and waivers - Define signable documents and the rules that require them, including household-role targeting for children.
  • Accounts - Household accounts and the Owner, Adult, and Child roles behind guardian signing.
  • Member profiles - See a single member’s signatures in the context of their record.
  • Settings overview - Where Waivers sits among the other settings.