Skip to main content

Signer Sessions: Prevent Conflicting Edits During Remote Signing

Signer Sessions protect your packets and documents from accidental overwrited when two or more signers open the same document at the same time.

Updated over a week ago

This guide covers how Signer Sessions work, what users will see, and how community staff can manage active sessions.

Why Signer Sessions Exist

In real-life scenarios, like spouses sitting at the kitchen table completing move-in paperwork together, multiple people may open the same document at the same time. Previously, this could cause:

  • Overwritten responses

  • Lost data

Signer Sessions prevent these issues by managing access in real time.


How It Works (At a Glance)

  • When a signer clicks Sign, they begin an active signing session

  • Anyone else who has access to the same document will see:

    • A flag showing who is current signing

    • A read-only mode button

    • The Sign button disabled

  • The system updates in real time so non-signers can still follow along in “read-only”

  • Community users can view active sessions and end a session if needed


Scenario 1: Two Signers Try to Sign at the Same Time

What the first signer sees:

  • They open the packet and select Sign on the document

  • The document opens fully editable

  • A banner does not warn them yet - because they are the active signer

What the second signer sees:

  • They open the same packet and navigate to the same document

  • The Sign button is disabled

  • They can only view in Read-Only

  • A badge shows who is currently signing (eg. Signing in Progress: [email protected])

  • When selecting read-only they get a modal explaining why editing is locked

Scenario 2: Viewing Live Updates While Someone Else is Signing

Even in read-only mode, other collaborators can:

  • View the document

  • Watch updates appear in real time as the active signer completes fields

  • Return to the packet overview at any time

  • Work in any other open documents

Scenario 3: Community Managers Ending an Active Sessions

Sometimes a signer may:

  • Leave their device idle

  • Close their browser without exiting

  • Get stuck

  • Block another signer who needs access

Community users now see active session indicators directly in the packet on the document list.

Steps for community users:

  1. Open the packet

  2. Navigate to the documents tab

  3. Look for the document with a ‘Signing in Progress’ flag

  4. Click the kebab; select View Active Sessions

  5. A modal displays showing:

    • Active signer name and email

    • Signer type (resident or collaborator)

    • Device information

    • Date stamp

  6. Click ‘End Session’ to immediately unlock access for others.

Scenario 4: After a Session Ends

When a session is ended by community staff:

  • The signer sees a message: “Your signing session was ended by the community. Your changes have been saved.”

  • They can return to the packet and wait until the document becomes available again

  • Other signers can now click Sign and take over


Troubleshooting & FAQs

What if a signer things the session is locked by error?

  • They should contact the community or wait for the active signer to exit.

Will any data be lost when a session ends?

  • No. All entered data saved automatically before the session closes.

Can two signers view the document at the same time?

  • Yes — but only one can actively sign.

Does this apply to Sign in Person?

  • Yes. Anytime multiple devices could access a packet at once, Signer Sessions protect the data.

Did this answer your question?