# Quick start

> Add proxies, add a Steam account & run your first task.


This walks you through the three things every new account starts with: proxies to log in through, a Steam account to automate, and a first task to prove it all works. Takes about five minutes.

## 1. Add your proxies

Start here, not with accounts. SteamLabs never logs a Steam account in without a proxy, so an account with nothing available simply will not sign in.

Open **Proxies** under **Management**. Before you add anything you will see a notice that your accounts are using our shared pool. That pool works, but it is shared with every other user and it stops at 50 accounts, so add your own as soon as you can.

![The proxies page with no proxies added](/images/docs/quickstart-proxies-empty.png "The proxies page before you add anything, with the shared pool notice at the top.")

Use **New Proxy** for a single proxy, or **Import** to paste a whole list at once. Import takes one proxy per line in any of these shapes:

```text
host:port
host:port:user:pass
host:port@user:pass
user:pass@host:port
```

Each line can start with `http://` or `socks5://`. Anything without a prefix uses the **Default protocol** you pick in the modal, and duplicates you already own are skipped.

![The proxy import modal with a list pasted in](/images/docs/quickstart-proxy-import.png "Paste one proxy per line. The helper text under the box lists every format that parses.")

New proxies land in the list as `Untested`. Hit **Test all** to check them, your workers will report back latency and the exit IP each one actually comes out of.

> [!TIP]
> Leave proxies unassigned and your accounts will use your whole pool. Pin a proxy or a proxy group to specific accounts only when you want an account to keep one fixed IP.

## 2. Add a Steam account

Go to **Accounts** under **Management** and press **New Account**.

![The create account form](/images/docs/quickstart-account-create.png "Username & password are required. Both secrets are optional but worth adding.")

**Username** and **Password** are required. **Shared Secret** and **Identity Secret** are optional.

Have more than one account? Skip the form: **Import CSV** takes a spreadsheet (a header row plus `username` and `password` columns, secrets optional), and **Import maFiles** takes your `.maFile` exports. maFiles carry no password, so add a passwords file alongside them with one `username;password` per line.

Importing more than a hundred maFiles at once? Zip them up and drop the archive into the same modal instead of picking the files one by one. Subfolders are searched too, so zipping your whole maFiles folder works, and anything in there that is not a `.maFile` is ignored.

After you save, you land on the account page, and almost everything on it saids `Not fetched yet`. That is expected. SteamLabs has your credentials, but it has not talked to Steam yet.

![A newly added account before any task has run](/images/docs/quickstart-account-before-refresh.png "The account page right after saving, before any task has run.")

## 3. Run your first task

**Refresh Details** logs the account in and pulls back everything Steam knows about it: profile, wallet, games, bans, inventory. It is the task to run first, because most other pages stay empty until it has.

For a single account, open it and pick **Refresh Details** from **Quick actions**.

![A new account with the Quick actions menu open](/images/docs/quickstart-quick-actions.png "The Refresh Details task in the Quick actions menu.")

For more than one account, go to **Tasks** under **Automation** and press **Create tasks**: pick your accounts, then pick the type. **Refresh Details** sits at the top of the **Account** group.

![The task type picker with Refresh Details highlighted](/images/docs/quickstart-task-type.png "Task types are grouped by what they touch. Refresh Details is the first one under Account.")

Submit and you land back on **Tasks** with your new task queued.

![The tasks list with a queued Refresh Details task](/images/docs/quickstart-task-queued.png "A fresh task waiting for a worker to pick it up.")

From there it moves on its own: `status:queued` while it waits for a free worker, `status:running` once one picks it up, then `status:completed` or `status:failed`. Open the task to watch its log lines stream in, along with the worker and proxy it used.

Pick the same type for several accounts and you get one batch row instead, with a live count of how many are done.

> [!NOTE]
> Nothing retries by itself. A failed task stays failed until you press retry, which queues a fresh one.

## What changed

Once the task completes, go back to **Accounts**. The row that was empty now has an avatar, a wallet balance, an item count, and **Details Refreshed** has flipped from `Never` to a few seconds ago. Your inventory shows up under **Inventory**, and the account is ready for everything else: profiles, trading, selling.