PropertyBoss eSign allows you to send documents created through the Letters module for electronic signature using Dropbox Sign, formerly HelloSign. eSign documents begin as PropertyBoss Letters but require Microsoft Word, special eSign merge fields, and an internal signer to complete the signing process.
TABLE OF CONTENTS
- Before You Begin
- Create the Letter Template
- Add Your Signers
- Add eSign Fields
- Follow eSign Template Formatting Guidelines
- Understand the Signing Sequence
- Verify Signer Information Before Sending
- Send the eSign Document
- Monitor the Request
- Send a Reminder
- Change the Internal Signer
- Cancel an eSign Request
- What Happens After Each Person Signs?
- Complete the Internal Signature
- Find the Completed Document in PropertyBoss
- Best Practices
- Need Help With an Existing Request?
Before You Begin
Before creating an eSign document:
- eSign must be activated for your PropertyBoss database. eSign is a standard PropertyBoss feature with no additional usage or signature fees, but activation by PropertyBoss may be required.
- The PropertyBoss user must have the appropriate security permission to use eSign.
- The Letter must be created using Microsoft Word.
- Every eSign document must include an internal PropertyBoss signer.
- Verify that the email address stored in PropertyBoss for each resident or guarantor is correct before sending.
Important: The built in PropertyBoss Word Processor can be used for standard Letters but cannot be used to create eSign documents. Microsoft Word is required for eSign.
Create the Letter Template
Start by creating the document through the PropertyBoss Letters module.
- Select the appropriate Letter category.
- Create a new Letter using Microsoft Word.
- Add the standard PropertyBoss merge fields needed in the document.
- Add and format the document content.
- Add the appropriate eSign fields for each signer.
- Review and test the template before using it with an actual eSign request.
Add Your Signers
PropertyBoss uses specific eSign fields to identify each person who participates in the signing process.
Resident Signers
- Use E1 through E6 for resident signers.
- A document can include up to 6 resident signers.
Guarantor Signers
- Use EG1 through EG6 for guarantor signers.
- A document can include up to 6 guarantor signers.
Internal Signer
- Use EI1 for the internal PropertyBoss signer.
- Each eSign document must include one internal signer, and EI1 is always the final signer in the signing sequence.
Important: Every person included in the eSign workflow must have a corresponding signature field. Other fields such as initials, dates, text, or checkboxes can be added as needed, but they do not replace the required signature field.
Add eSign Fields
eSign fields tell Dropbox Sign what each signer must complete. PropertyBoss supports eSign fields for:
- Signatures
- Initials
- Dates
- Text
- Checkboxes
All eSign fields placed in the document are required. The signer must complete all fields assigned to them before completing their portion of the signing process.
Select Fields from the Merge Field List
Whenever possible, select eSign fields directly from the PropertyBoss merge field list. Although eSign fields can technically be entered manually, they must match the recognized PropertyBoss merge field exactly. Selecting the fields from the merge field list helps prevent typing errors that could keep PropertyBoss from recognizing the field.
Follow eSign Template Formatting Guidelines
eSign documents are created in Microsoft Word, but there are some important formatting requirements and recommendations to keep in mind.
Headers and Footers
Do not place PropertyBoss merge fields or eSign fields in a Microsoft Word header or footer. Merge and eSign fields must appear within the body of the document to function correctly.
Tables and Text Boxes
- Tables and text boxes are supported, but PropertyBoss recommends avoiding them when possible.
- The actual information inserted into a merge or eSign field can vary in length. For example, one name or signature may require significantly more space than another. When the real information is inserted, a table or text box may expand and shift other document content or formatting.
- Keeping the document structure simple helps reduce unexpected formatting changes.
Images
Images such as a company logo or letterhead can be placed before the merge and eSign fields on the page. Avoid placing images after merge or eSign fields.
Document Protection
Do not password protect, restrict editing, or apply other document protections or restrictions to a Microsoft Word document used for PropertyBoss eSign.
Multiple Pages
eSign documents can contain multiple pages and page breaks. No special configuration is required simply because a document contains multiple pages.
Understand the Signing Sequence
PropertyBoss eSign uses a sequential signing process. The document is first sent to E1. After E1 completes all required fields and signs, the document automatically moves to the next signer.
- For example: E1 → E2 → EG1 → EI1
In this example:
- E1 receives and signs the document.
- After E1 signs, E2 automatically receives the document.
- After E2 signs, EG1 receives the document.
- After EG1 signs, EI1 receives the document.
- EI1 completes the final signature.
The request is not considered complete until EI1 has signed.
Important: A later signer will not receive the document until the signer before them has completed their portion. If E2 has not received an email while E1's signature is still outstanding, this is expected behavior.
Verify Signer Information Before Sending
eSign requests are automatically routed using the email address associated with each signer in PropertyBoss. Before sending, verify:
- The correct people are included.
- Signers are assigned in the correct order.
- Each signer has a corresponding signature field.
- All other required eSign fields are assigned to the correct signer.
- Each resident and guarantor has the correct email address in PropertyBoss.
- The appropriate PropertyBoss user is assigned as the internal signer.
- The generated document contains the expected merged information.
Important: If an external signer's email address is incorrect after the request has been sent, the request must be cancelled and resent after the email address is corrected. Change Signer cannot be used to correct a resident or guarantor email address.
Send the eSign Document
Once the document and signer information have been verified, PropertyBoss provides two sending options:
Send Now
Send Now begins the eSign process without the additional review step.
Review and Send
Review and Send provides an opportunity to review the generated document and signer information before releasing the eSign request. For a new or recently modified template, reviewing the document before sending is recommended.
Monitor the Request
After sending, use the Letters >Document Status area in PropertyBoss to monitor and manage the request. From this area, authorized users can:
- View the current status
- Send a reminder
- Change the internal signer
- Cancel an outstanding request
- View completed requests
- View cancelled requests
Send a Reminder
If the current signer has not completed the document, you can send a reminder from the Document Status area. The reminder is sent only to the signer whose turn it currently is.
Dropbox Sign sends that person a new signing link. After a reminder is issued, the previous signing link will no longer work.
Tip: If a signer reports that their link is expired or invalid after a reminder has been sent, ask them to use the link in the most recent Dropbox Sign email.
Change the Internal Signer
The Change Signer option in PropertyBoss applies only to the internal signer, EI1. Use this option if a different PropertyBoss user needs to complete the final internal signature. Changing the internal signer does not alter the contents or integrity of the document that has already been sent, so the request does not need to be cancelled and resent.
Note: Change Signer cannot be used to replace a resident or guarantor or correct an external signer's email address.
Cancel an eSign Request
If the document needs to be changed after it has been sent, the existing request must be cancelled. Cancelling a request:
- Stops the signing process immediately.
- Makes previously issued signing links unusable.
- Leaves the cancelled request visible in the Letters area for historical reference.
After cancellation, make the necessary changes and send a new eSign request.
The same process is required when an external signer's email address needs to be corrected.
What Happens After Each Person Signs?
After a person completes their portion of the signing process, they receive an emailed copy of the document. That copy represents the document at that point in the signing sequence. For example:
- E1 receives a copy showing E1's signature.
- After E2 signs, E2 receives a copy showing E1's and E2's signatures.
- Each subsequent signer receives a copy containing the signatures completed before them as well as their own.
The document then continues to the next person in the signing sequence.
Complete the Internal Signature
After all required residents and guarantors have signed, the document is automatically sent to the designated internal PropertyBoss signer, EI1. EI1 always signs last.
Until EI1 signs:
- The request remains incomplete.
- The final version is not yet saved to the PropertyBoss Media tab.
Once EI1 signs, the eSign process is complete.
Find the Completed Document in PropertyBoss
After the internal signer completes the final signature, the final completed version is automatically saved in PropertyBoss. PropertyBoss saves only the final version. Intermediate versions generated during the signing sequence are not stored in PropertyBoss. The final document includes:
- All completed signatures
- The complete signing audit trail
Where the document is stored depends on the status of the signer in PropertyBoss.
- Current resident with an active lease: The completed document is saved to the Media tab of the Lease Notebook.
- Prospect or other contact without a lease: The completed document is saved to the Media tab of the Contact Notebook.
Because EI1 signs last, the internal signer also receives an emailed copy containing all signatures and the complete signing history.
Best Practices
Before putting a new or significantly changed eSign template into regular use:
- Test the template.
- Confirm that merge fields populate correctly.
- Confirm that every signer has a signature field.
- Review all additional eSign fields.
- Verify signer order.
- Verify external signer email addresses in PropertyBoss.
- Review the document for unexpected formatting changes.
- Confirm the correct internal signer.
- Use Review and Send when additional review is appropriate before releasing the request.
Simple Word document formatting is generally the safest approach, particularly when merge fields or signature fields can vary significantly in length.
Need Help With an Existing Document?
For help with missing signing emails, expired or invalid links, reminders, cancelled requests, signer changes, or other common issues, see: eSign FAQ & Troubleshooting