Reviewing and Approving

Shuttlebase builds and runs the experiments, but you keep the final say. Whenever a decision needs your sign-off, a pending action appears in your dashboard. This page covers the four kinds of requests you will see and what each response does.

Note

Only users with the approve pending actions permission can respond to requests. See Users and Permissions.

Reviewing a launch request

You get an email when a new experiment is ready for review. In the dashboard, the launch request shows you each variant with its details and screenshots, and you can preview the variant live. A QR code lets you open the mobile version on a real device. You respond to each variant on its own, and you have five options.

• Approve. The variant launches as built.
• Request changes. Describe what you want changed in plain language and attach screenshots. Shuttlebase implements the changes, runs the variant through QA again, and sends you a new approval request.
• Reject. The variant is removed from the experiment and its traffic is reallocated.
• Propose an alternative. Suggest your own version of the change for Shuttlebase to build instead.
• Approve with your own edits. Make edits to the variant yourself, then approve the edited version.

What happens after you respond

If at least one variant is approved and none need changes, the experiment moves straight to the launch queue as Approved: Pending Launch. From there the scheduler launches it automatically. See Experiment Lifecycle for how launch timing works.

If any variant needs changes, the experiment moves to Pending Modifications. Shuttlebase makes the changes, the variant passes the full QA gate again, and you receive a launch after modifications request.

Rejected variants are removed entirely. Their share of traffic is redistributed across the remaining variants, so rejecting one variant never delays the rest of the experiment.

Reminders

If a request sits unanswered, Shuttlebase sends you email reminders until you respond. A waiting request holds the experiment in place, so responding quickly keeps your testing program moving.

Tip

You can reduce how many requests you receive. Automation Settings let Shuttlebase end losing experiments or deploy winners automatically instead of asking each time.