Skip to main content

Advanced settings for your test

Where to find notifications, team access, templates, integrations, and secure file sharing for a single test.

Every test has an Advanced Settings page that holds the optional settings for that one test: who gets email notifications, which colleagues can see it, whether it pushes issues to Jira, whether it opens a discussion forum, and whether you can share files securely with testers.

Nothing on this page is required to launch a test, but each section changes how you and your team work through it. Turn on notifications if you want to hear about issues as they arrive rather than checking the test every morning. Invite your team if a colleague needs access to a single test. Connect Jira if your engineers never log in to BetaTesting. Create a forum if you want testers talking to each other about your product.

To open it, go to a test and click Advanced Settings in the left menu. Every section starts collapsed, so click a heading to open it. What you see depends on your access level, your plan, and the type of test, so you may not see all of the sections below.

Notifications

The first group of checkboxes sets what BetaTesting emails you about for this test. Tick any of them to get an email each time the event happens:

  • New issue submissions

  • Issue comments for issues that you watch

  • Messages & replies

  • Survey submissions

  • System notifications, which covers alerts that the test end date is approaching, reminders to review testers before the review period ends, and changes to invite status

Below those is Receive a daily digest, a nightly summary of new activity across every test you manage. That one is a company-wide setting rather than a per-test one, so changing it here changes it everywhere.

Read-only admins can see these settings but cannot change them.

Invite your team

Click Add Team Member to give a colleague access. You enter their name, their email address, and an access level:

  • Admin gives full functionality.

  • Customer Support can message testers, respond to issues, and view all results, but cannot edit the test instructions or settings.

  • Read-only can view results only.

If you have set up business groups in your company settings, you can also assign the person to a group so they only reach that group's tests. Your plan sets how many team members you can add, so the button is disabled once you reach the limit.

This section is visible to full admins only.

Test template

Tick Use as template to mark the test as a template so it can be cloned when new tests are created from your community. This section only appears if templates are included in your plan.

Jira integration

Click Setup Jira Integration to connect this test to a Jira project so issues submitted by testers become tickets in Jira. The connection applies to this test only. See push issues to Jira for the full walkthrough, including credentials, field mapping, and auto-push.

This section is visible to full admins only.

Discourse integration

Tick Create a Discourse forum for this test upon test launch to give your testers a private discussion forum that opens when the test goes live. If forums are not included in your plan, the option is disabled and BetaTesting invites you to contact the team.

This section is visible to full admins only.

Secure file directory

Click Setup Secure Files to upload files you want to share with testers through links or a file directory rather than a public download. This section appears on multi-session tests before they go live. Once a test is live, secure files move out of Advanced Settings and become a Secure Files item in the test's left menu.

BetaTesting admin settings

This section is visible to BetaTesting staff only. If you do not see it, nothing is missing from your account.

Things to know

  • Almost everything here applies to one test. Notification choices, team access, and the Jira connection do not carry across when you duplicate a test. The daily digest is the exception, because it is set once for your whole company.

  • Changes save as you make them. A Changes saved or Saved confirmation appears next to the section rather than at the bottom of a form.

  • Sections you do not have access to simply do not appear, so two people looking at the same test can see a different list.

Related articles

Did this answer your question?