General Settings

The General tab is where you manage the core identity of your project — its name, the website it belongs to, a short description, which environment it runs in, and whether it is currently active. These settings affect how your project appears across the platform and how your team works with it.

Accessing the General tab

Open your project, click the gear icon in the left sidebar to open Project Settings, then select the General tab. This is the default tab when you open settings.

Fields

Project name

The name used to identify your project throughout A vs B — in the project switcher, the dashboard header, experiment lists, and reports. This field is required. Choose a name that clearly describes the website or app the project belongs to, such as "Main Website", "US Storefront", or "Marketing Blog".

Domain / URL

The full web address of the website this project represents, including the protocol — for example, https://www.example.com. A vs B uses this URL to:

Detect whether the snippet is installed and returning correctly
Generate the correct snippet tag pre-filled with your key
Validate that experiment URLs match your project domain

This field is optional, but filling it in enables snippet detection and is strongly recommended.

Description

A free-text area where you can add notes about the project — its purpose, the team that owns it, or any context that helps new members understand what it represents. The description is visible only to team members inside A vs B. It does not appear on your public website.

Environment

The environment selector lets you label this project according to where it runs in your deployment pipeline. There are three options:

Production — your live website visited by real users. Experiments running in this environment have real business impact. This is the correct choice for most projects.
Staging — a pre-production environment used for internal testing and quality assurance before releasing to production. Use this if you want to test experiments before they go live.
Development — a local or team-internal environment. Useful when developers want to test snippet integration or experiment rendering during active development.

The environment label is for your reference only. All three environments behave identically in terms of how experiments run. Choosing "Production" does not grant any special permissions, and choosing "Development" does not restrict anything.

If you run experiments across production and staging separately, create one project per environment and give each its own snippet key. This way staging experiments do not mix with production data.

Status

The project status controls whether experiments in this project can be active. There are three statuses:

Active — the project is live. Running experiments execute normally, and new experiments can be published. This is the default status for new projects.
Paused — all running experiments in the project are suspended. Visitors see the control variation (or no variation) until the project is set back to Active. Use this during a major release, an incident, or a planned maintenance window. You can still view reports and edit experiments while a project is paused.
Archived — the project is retired. It is hidden from the project switcher and the main project list. No experiments run. Archived projects and their historical data are still accessible from the archived projects view, but no new experiments can be created or published.

Setting a project to Paused immediately stops all currently running experiments. Visitors will no longer be bucketed into variations. Experiment data collection also stops. When you set the project back to Active, experiments resume automatically.

Last updated

At the bottom of the General tab, A vs B displays a Last updatedtimestamp showing when these settings were most recently saved and which team member made the change. This is useful for auditing who last modified a project's configuration.

Reset and Save

The General tab has two action buttons at the bottom of the form:

Reset — discards any unsaved changes and restores the fields to their last saved values. Use this if you started editing and want to undo everything without saving.
Save — commits all field changes to your project. You will see a confirmation message when the save is successful.