> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.conductorquantum.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.conductorquantum.com/_mcp/server.

# Get started with Control

> Access your existing lab and connect your own computer to Control.

[Control](https://control.conductorquantum.com) runs experiments on lab instruments, analyzes the results, and tracks jobs, plots, and calibrations in one web app. This guide is for users accessing an existing lab. Contact Conductor Quantum Admins if your lab or instruments are not available.

Looking for the `conductorquantum` Python SDK and hosted analysis models instead? Use the [Models quickstart](/control/getting-started/quickstart). The SDK and the Conductor CLI serve different purposes.

## Before you start

* Sign in to [Control](https://control.conductorquantum.com). Ask your lab manager for an invitation to your existing lab, then accept with the matching verified email.
* Confirm that you are authorized to use the instruments you need. If the lab or an instrument is unavailable, contact Conductor Quantum Admins before attempting a run.
* To use your own instrument-control code, obtain the approved Conductor CLI and user-side installation instructions from your Conductor contact. Use the same operating-system account for installation, login, and startup. You do not need the CLI just to use the web app.

## Connect from your own computer

You can use the web app to [run jobs and inspect results](/control/usage). If you also need to connect an existing instrument client or notebook to your authorized instruments, install the approved CLI on that computer and run:

```sh
conductor login --profile user
```

Approve the requested lab access in Control and keep the process running. In a second terminal, list your local endpoints:

```sh
conductor connections --profile user
```

Point your instrument client at the printed loopback host and port; do not assume it uses the instrument's original port. Resume a stopped user profile with `conductor start --profile user`. Use the Control deployment your lab has authorized; production is the CLI default.

> **Warning**
>
> Private-network connectivity is not permission to operate an instrument. Lab membership, instrument authorization, and per-job hardware controls still apply. Check your targets, experiment settings, and approved safe operating limits before running an experiment.

Continue with [Control usage](/control/usage) to submit your first job.