Set up Testbench

Testbench gives a project a private place to run product tests with people outside your workspace. Testers can read assigned instructions, answer surveys, send feedback, and manage their own data. They do not become workspace members and do not use workspace seats.

Project owners and administrators can open Project Settings → Testbench → General and turn on Enable Testbench. Enabling the module creates an invite-only program. It does not invite a tester, open public enrollment, publish a round, or send email.

Open Modules → Testbench for daily work. Its tabs are Overview, Testers, Rounds, Feedback, and Email. Use the Settings button for enrollment, branding, custom domain, and data retention.

The setup wizard keeps tester recruitment inside Testbench. Its Add testers step lets an operator edit the invitation message, add testers, and review the roster. The required access invitation can be sent before the tester gives participation or optional-email consent. Launch updates are optional email and require that later consent.

Pausing Testbench stops normal tester access and new active work. It keeps tester records, round history, feedback, settings, and privacy controls. Existing history also stays readable after a subscription downgrade.

Subscription limits

Testbench requires Pro, Business, or Enterprise. Pro includes 250 counted testers per workspace and five active rounds per project. Business includes 2,500 counted testers and 25 active rounds. Enterprise uses its contract limits.

Invited, accessed, testing, complete, and paused testers count toward the workspace limit. Pending applications do not count. Withdrawn and blocked testers do not count. Pausing the module does not free tester capacity.

Support and Testbench share the external-project allowance. If both modules are active on the same project, they use one slot. Pro includes three external-enabled projects. Business includes ten. Enterprise uses its contract allowance.

Portal access and branding

Tester pages use testbench.tododdle.com. The root page is neutral and does not list projects. Testers sign in through a private email link. A session lasts seven days and grants access only to that project's assigned rounds. A ToDoddle app session does not sign a tester into Testbench.

Use Project Settings → Testbench → Enrollment to choose Invite only, Applications, or Open signup. Use Project Settings → Branding for shared portal colours and images. Use Testbench → Portal for welcome, invitation, and completion text. Invitation emails use the saved invitation text, display name, email identity, accent colour, and logo. The email embeds the saved logo instead of loading it from a remote address. It also shows the project name as text, so the brand and button remain clear if a client hides images.

Business and Enterprise can add a verified custom hostname. Testbench and Support share one domain registry, so one hostname can belong to only one portal. The default Testbench address keeps working after verification.

Private access tokens stay in the link fragment and are not sent as a query string. Do not copy private tester links into tickets, Context, analytics, or logs.