The signing experience itself is simple for customers, and documents sent from our team account were stored securely. When everything lives in the organization account, it works fine for day-to-day e-signatures. Review collected by and hosted on G2.com.
SignRequest lets employees create personal accounts using the company's email domain, even when that domain already has a paid team account. Those personal accounts are not linked to, visible from, or recoverable by the organization.
We needed signed documents and audit trails from 2021 for a legal matter. The documents had been sent by a former sales rep from a personal account registered to his company email, before his activity started showing up in our team account. Support would not retrieve or transfer the records, even though the account was on our domain and we offered to verify our authority. Their only option was to recreate the departed employee's mailbox, log into his old account, and buy a paid subscription just to access the documents.
We did that and got what we needed. When we then asked to cancel the subscription we had just been required to purchase and refund the charge, support declined because it wasn't the account's first invoice, and said only the account owner could cancel. The charge was small. The issue is the principle: we were told to pay to unlock our own company's records, then refused a refund on a subscription we only bought because support told us it was the only path.
For a product whose core value is document retention and a reliable audit trail, allowing unmanaged shadow accounts on a company domain is a real compliance and legal risk. Most enterprise SaaS tools either block this or let the domain owner claim those accounts. SignRequest does neither. Review collected by and hosted on G2.com.
