/members/document-signatures). The signable documents and the rules that require them are configured separately under Settings > Operations > Documents & Waivers.
Overview
- Signature ledger - One row per member and document, showing the latest acceptance with its status, date, and signature type.
- Signature detail - Open a row to see the full signing history, the document version, the typed name, and captured evidence.
- Typed-name acceptance - When a document rule requires it, the member’s typed full name is recorded and shown on the signature.
- Signing evidence - Drawn-signature image, acceptance timestamp, IP address, and device / user agent, captured by the signup wizard.
- Guardian / proxy signing - A dependent’s document can be accepted by their guardian; the ledger records the dependent as the subject and the guardian as the signer.
- Signed agreement PDF - Download the rendered membership agreement (member details, household, accepted documents, and signature) on demand.
The signatures list
The list shows the most recent acceptance per member and document, 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 when an acceptance exists, or Pending when the document is required but not yet signed.
- Signed Date - When the latest acceptance was recorded.
- Type - Electronic (signed online) or Physical (a paper acceptance recorded in the system).
Signature detail
Click any row to open its detail page.- Signature details - The document (a link to its content item), the signed date(s), and the signature type.
- Signed history - Every acceptance for that member and document, newest first, each with its timestamp and the document version at signing time. Because a document can be re-signed (for example after a new version), the history preserves each event rather than overwriting it.
- Status - Signed or Pending.
- 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 signer.
- 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.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 and proxy signing for dependents
When a household enrolls a dependent (for example a parent registering a child for a kids’ program), the guardian accepts the dependent’s documents on their behalf during the signup wizard. In the ledger:- The subject of the signature is the dependent - the row belongs to the child’s contact and appears under their profile.
- The signer is the guardian - the acceptance is attributed to the account owner who actually completed the wizard.
dependent 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 dependent’s required documents are presented to the guardian, and each accepted one is recorded as a separate signature for the child.
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 dependents.
- 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.
- Acceptance link - Staff can generate an acceptance link for a specific member and document (an e-signature token), which opens the document for that member to review and accept.
- Physical record - A paper acceptance can be represented as a signature of type Physical.
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 Pending row 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 dependents, expect the signature to sit on the child’s record with the guardian as signer - that is the intended proxy model, not a data error.
Troubleshooting
Related
- Documents and waivers - Define signable documents and the rules that require them, including household-role targeting for dependents.
- Accounts - Household accounts and the owner/adult/dependent roles behind guardian signing.
- Member profiles - See a single member’s signatures in the context of their record.
- Settings overview - Where Documents & Waivers is configured.