Take the guided tour
Open the ledger in the studio and read it together.
What a signature records
Each row is one person, and it never changes. There is no editing a signature and no un-signing, because a record you could revise would not be evidence.The IP address and user agent are captured by Userplay at the moment of signing, never sent by the signer. That is what makes them worth having: the studio attests to the circumstances, not the person agreeing.
Check everyone holds the same terms
Open the Analytics tab. On current version compares every signature against the agreement as it reads today. If that number is lower than the total, signatures span more than one revision, and a Document versions breakdown appears showing how they split. That happens when you published a second NDA with revised terms and some people signed the earlier one. Anyone on an older revision agreed to something different. Decide whether that matters before you rely on it.Export a copy you can file
Click Export on the Signatures tab. You get a CSV with every column above, covering the whole ledger rather than the page on screen.The roster is the same people
Every signer lands on the NDA’s backing roster, which shows up under Player groups as an NDA roster. You cannot edit it by hand: its membership is the signature ledger, and adding someone without a signature would say something that is not true. What you can do is pull it into a playtest, which is usually the point.Related articles
Signatures
The full field reference.
NDA analytics
Totals, the trend, and the revision split.
Send out an NDA
The full walkthrough, start to finish.
Build a group you can reuse
Pull the signer roster into a playtest.