NDA Management

The NDA module lets you require testers and support staff to sign a Non-Disclosure Agreement before they can submit bug reports, suggestions, or upload files to your project. This is useful for studios sharing pre-release builds or confidential materials with playtesters.

Enabling the NDA Module

To enable the NDA module:

1. Go to your project’s settings page
2. Find the Modules section
3. Check the NDA module
4. Save your changes

Once enabled, a new NDA Management link appears in the project sidebar (visible to Developers and organization Admins).

Creating an NDA Version

Navigate to NDA Management and click Create New Version.

You can provide your NDA in three ways:

• Markdown text — Write the agreement directly in the editor using Markdown formatting
• PDF attachment — Upload a PDF document
• Both — Provide Markdown text for inline viewing plus a downloadable PDF

First Version Options

When creating your first NDA version, you’ll see a checkbox: Require all current testers and support staff to sign this NDA. If checked, every existing non-developer member will immediately be required to sign. You can always adjust individual requirements later from the NDA Status page.

NDA Settings

After creating your first version, the management page shows an NDA Settings section:

• Require NDA for new members who join — When enabled, anyone who joins the project (via invite link or the Join button) will automatically be required to sign the NDA. This setting only takes effect when an NDA version exists.

Managing NDA Requirements

NDA requirements are controlled per member. From the NDA Management → NDA Status page, you can see every tester and support staff member with their current NDA status.

Individual Control

Each member row has an action button:

• Require NDA — For members not currently required to sign
• Remove Requirement — For members who are required but haven’t signed yet (members who have already signed don’t show a remove button)

Bulk Actions

Use the checkboxes to select multiple members, then use the action bar that appears at the bottom:

• Require NDA — Set NDA as required for all selected members
• Remove NDA Requirement — Remove the NDA requirement for all selected members

Use the Select all checkbox in the header to quickly select everyone. Members who have already signed are excluded from the selection.

Tester Experience

When a tester who is required to sign tries to access the project — including viewing it, submitting a bug report or suggestion, or uploading files — they are redirected to the NDA acceptance page.

The acceptance page shows:

• The NDA text rendered from Markdown (if provided)
• A download link for the PDF (if attached)
• A checkbox: I have read and agree to the terms of this Non-Disclosure Agreement
• An Accept NDA button

The tester must check the agreement checkbox and click Accept NDA to proceed. Their acceptance timestamp, IP address, and browser information are recorded for compliance purposes.

After accepting, the tester is redirected to the page they were originally trying to access.

NDA Status & Signers

The NDA Status page provides a complete overview of NDA compliance across your team.

Status Indicators

Each member shows one of three statuses:

• Signed — Member has accepted the current NDA version, with the acceptance date shown
• Pending — NDA is required but the member hasn’t signed yet
• Not required — NDA is not required for this member

CSV Export

Click Export CSV to download a CSV file with all member NDA data, including:

• User, email, and role
• Whether NDA is required
• Current status (Signed, Pending, or Not required)
• Acceptance date and IP address (for signed members)

Updating Your NDA

To publish a revised NDA, go to NDA Management and click Create New Version. When creating a subsequent version, you’ll see an additional option:

• Require re-acceptance from existing signers — If checked, members who signed a previous version will need to accept the new version as well. If unchecked, their previous acceptance carries over and they won’t be interrupted.

This lets you handle minor wording changes (no re-acceptance needed) differently from significant legal updates (re-acceptance required).

Invitations & NDA

When creating invitation links for your project, you’ll see a Require NDA acceptance checkbox on the invitation form. This behaves based on your NDA configuration:

When a new member joins through an invitation with NDA required, they will be prompted to accept the NDA before they can access the project.

See Also

• Project Settings – Configure project modules and settings
• Joining Projects – How testers find and join projects
• Organizations – Plan management and team structure