At a Glance
When contributors initially join the UserTesting Contributor Network and each time they sign in, they agree to the Terms of Service that includes a broad NDA (non-disclosure agreement) from UserTesting which prohibits them from sharing information about your site or app when providing feedback in your test. For this reason, most of our customers choose not to require an additional NDA.
While you don't need to administer your own NDA for your UserTesting tests, you always have the option to require contributors to sign your company's NDA before accepting your test, provided that such additional confidentiality terms do not conflict with or supersede the confidentiality terms already in effect between UserTesting and the contributor.
You can administer NDAs to contributors with one of the following methods:
- Option 1: Set up your own electronic signature with your company’s NDA and place the NDA as the first task within a test.
- Option 2: Set up your own electronic signature with your company’s NDA and have contributors sign it as part of a stand-alone (pre-screening) test.
Option 1. Set up your own electronic signature with your company's NDA and place the NDA within a test.
To include your own NDA, you can set up an NDA document through Adobe Sign (formerly EchoSign), DocuSign, a Google form, or another option of your choice. Here's a sample Google Form.
Since you are using your own systems and providing the URL to the contributors in your test, there is no additional cost; contributors complete the form at the same time they are completing your test, which keeps things simple. However, with Option 1, there is a risk that a contributor could encounter a problem with your NDA link and fail to sign it, but still continue with the test. If your test materials are especially sensitive, we recommend exploring Options 2.
- Create a screener question that informs contributors they need to sign an NDA to participate in the session, and that failure to sign the NDA before proceeding in the session will result in "a 1-star rating."
Pro Tip: Some contributors may not be comfortable signing your NDA, so give them an option to decline.
- In the first task, include a shortened URL to your online NDA (you can use a site like bitly.com to shorten the URL).
- If there are multiple steps (for example, Abobe Sign requires email verification), follow up with a multiple-choice question asking contributors to confirm that they've completed the second step.
Note: Adding your NDA in the tasks allows you to visually confirm their completion of the NDA. However, this process is based on the honor system, and if your test materials are especially sensitive, we recommend exploring Options 2.
Example: Provide information about the NDA in a screener question.
Place the NDA in a task:
Note: It's best to recruit a few additional contributors to ensure you receive enough completed tests.
Option 2. Set up your own electronic signature with your company’s NDA and have contributors sign it as part of a stand-alone (pre-screening) test.
This option is very similar to Option 1, except that the test only consists of the activity of signing the NDA. You can then observe if individuals sign the NDA (or look in the back-end of our system for managing NDAs).
- In the screener question, state that this test requires signing an NDA and those that sign will then be invited to another test to complete.
- Create a test with the tasks for signing an NDA. A short test can work well for this activity if you have that feature available.
- After identifying the contributors who do sign the NDA, use the Specific contributors function to send your full test to those specific contributors.
Need more information? Read these related articles.
Want to learn more about this topic? Check out our University courses.
Please provide any feedback you have on this article. Your feedback will be used to improve the article and should take no more than 5 minutes to complete. Article evaluations will remain completely confidential unless you request a follow-up.