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.
The NDA module is available on Standard plans and above. You can enable it from your project’s module settings.
Enabling the NDA Module
To enable the NDA module:
- Go to your project’s settings page
- Find the Modules section
- Check the NDA module
- 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
NDA versions cannot be edited after creation. Review your text carefully before submitting. If you need to make changes, you’ll need to create a new version.
Key Terms
Key terms is an optional table at the top of the NDA, like the Key Terms table many agreements open with. Use it when the agreement must name each tester: their legal name, country and address.
Each row has a label and is filled by one of:
- You — text you write, shown to every tester, such as the parties, the Purpose or Specific terms. Left empty, testers see “None”.
- Tester — a field the tester fills in when signing: Individual or company, Short text, Long text, Date or Checkbox. A row can be required and can carry a hint; for a checkbox, the hint is the text next to it, such as “I am 18 or older”.
- Signing date — the date the tester signs.
Add the usual rows adds Start date, Between, And, Purpose and Specific terms. And is an Individual or company row: the tester says whether they sign as an individual (full legal name, country of residence, street, city and postcode) or for a company (company name, country of incorporation, registered office address, their job title, and that they are authorised to sign for it). An NDA can have one such row and up to 20 rows in all. A new version starts from the current version’s Key terms.
When Key terms ask the tester for something, testers sign by typing their full legal name. Otherwise they tick a box to accept the NDA, as before.
Preview as Tester
Preview as tester opens the page testers will see, with your unsaved changes, in a window over the form. Fill it in and click Sign NDA to check which fields are required; nothing is saved.
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.
- Review signatures before granting access — Testers who sign wait until someone on your team approves them. See Reviewing Signatures.
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.
Developers and organization Admins are never required to sign the NDA. Only Testers and Support staff can have NDA requirements.
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.
If your project has public suggestions enabled, the NDA requirement does not apply to suggestion submissions, since those are open to the public by design.
The acceptance page shows:
- The Key terms table, with the fields the tester fills in (if your NDA has Key terms)
- The NDA text rendered from Markdown (if provided)
- A download link for the PDF (if attached)
When Key terms ask the tester for details, the tester fills them in, types their full legal name as their signature and clicks Sign NDA. When they sign as an individual, the typed name must match the full legal name they entered. Their answers are visible only to the project’s team.
Otherwise, the tester checks I have read and agree to the terms of this Non-Disclosure Agreement and clicks Accept NDA.
The acceptance timestamp, IP address and browser information are recorded for compliance purposes, together with the answers and signature.
After signing, the tester is redirected to the page they were originally trying to access, or waits for approval if you review signatures.
Signed Copy
A tester who signs by typing their name gets a signed copy by email: a PDF with the Key terms and their answers, the NDA text, the signature and a signing record (time, BetaHub account, IP address, NDA version and fingerprints). If the NDA has a PDF, its pages follow. Your team downloads the same copy with Signed copy on the NDA Status page.
Key Distribution waits for NDA acceptance: a tester on a key list receives the key, and the email with it, only once they accept the NDA.
NDA Status & Signers
The NDA Status page provides a complete overview of NDA compliance across your team.
Status Indicators
Each member shows one of these statuses:
- Signed — Member has accepted the current NDA version, with the acceptance date shown
- Awaiting approval — Member has signed and waits for your approval (when you review signatures)
- Approved — Member has signed and was approved (when you review signatures)
- Must sign again — Member signed an earlier version, and the current version needs a new signature
- Pending — NDA is required but the member hasn’t signed yet
- Not required — NDA is not required for this member
When your NDA asks testers who is signing, a Legal name column shows the name they gave and whether they signed as an individual or for a company. Search finds members by name, email or legal name.
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
- Acceptance date and IP address (for signed members)
- The tester’s Key terms answers, one column each (Signed as, Legal name, Country, Address and Job title for the individual-or-company row), and their typed signature
Reviewing Signatures
Turn on Review signatures before granting access in NDA Settings to check each signature, such as the legal name and address, before the tester can open the project.
- A tester who signs waits on a page saying the studio will approve them. Key Distribution hands out their key on approval.
- The project’s Developers get an email about signatures to review, at most one an hour per project.
- NDA Status shows how many signatures await approval, with Review the first one. Each waiting member has Review and Approve buttons.
The review page shows what the tester filled in, their signature with a check that it matches the legal name, and the signing record:
- Approve lets the tester in. They get an email.
- Ask to sign again removes their signature, with an optional message saying what to fix. They get an email and lose access until they sign again.
To approve several testers at once, select them on NDA Status and click Approve selected signatures. Switching review off lets everyone who is waiting in.
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).
A version whose Key terms ask testers for something the current version doesn’t always requires re-acceptance: earlier signers never gave those details.
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:
| NDA State | Checkbox Behavior |
|---|---|
| NDA configured (module enabled + version exists) | Checked by default, can be unchecked |
| NDA module enabled but no version created | Disabled with hint: “Create an NDA version first” |
| NDA module not enabled | Disabled with hint: “Enable the NDA module in project settings” |
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
- Team Identity & Privacy – Control how your team appears to players
- Key Distribution – Give testers game keys and see who got which