> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dashsquad.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Web Client
> Chat with your agents from any browser — no app to install.
Dash has a web client: a page you open in your browser to chat with your agents.
There's nothing to install. It works anywhere you have a browser and an internet
connection, and it uses the same [remote access](/remote-access) your phone uses to
reach your HQ.
The web client is a separate address from Desktop. Desktop still
runs on the machine with your agents; the web client is a page hosted elsewhere that
you can open on a laptop, a shared computer, or a phone browser.
## Before you start
The web client needs your HQ to already be set up for remote access. If you
haven't done that yet, follow [Remote Access](/remote-access) first — sign in to
Dash from Desktop, create your HQ, and confirm it shows **HQ
ready at** followed by your address.
## Sign in and chat
Go to the web client's address (your organization gives you this link — it looks
something like `https://app.`).
Sign in using a passkey — the fingerprint, face, or device unlock your browser
already offers. There's no password to remember.
If you have more than one HQ, choose the one you want to chat through.
The web client remembers your choice on this browser next time.
Open a conversation, or start a new one, and chat with your agent the same way
you would in Desktop or the phone app.
Conversations you have here are the same ones you see in Desktop and on
your phone. Anything you send from the web client shows up everywhere else too.
## Approve this device
If your account already has an iPhone or iPad signed in to Dash, a new browser needs
that device's approval before it can chat — this keeps someone who only has your
passkey from reaching your agents without you noticing. Instead of chatting right
away, you'll land on a screen headed **Approve this device**, with the message:
> Waiting for approval — scan this code with the Dash app on your phone.
Open Dash on your phone, go to **Settings**, tap **Approve a device**, and scan the
QR code shown here. A confirmation screen on the phone names this browser and
HQ — tap **Approve**, and this page continues automatically within a few
seconds.
Accounts with no iPhone or iPad signed in yet skip this step entirely: sign-in goes
straight to your HQ list, exactly as before. The moment your first Dash for iOS
device signs in, every new browser session after that needs approval.
If the request times out or is turned down instead, you'll see one of:
| What you see | What it means |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------- |
| Approval declined. You can try again from the HQ list. | Someone tapped Deny on the phone. If that wasn't you, check who else has access before trying again. |
| The code expired. Try again from the HQ list. | Nobody approved it in time. Go back to the HQ list to get a fresh code. |
## Manage your devices
Open **Devices** in the web client to see every browser that's signed in and
connected to this HQ. Click **Revoke** next to any browser you no longer
recognize or use — for example, a shared or public computer. Revoking your own
current browser signs it out immediately and sends you back to the HQ picker.
## Troubleshooting
| What you see | What's happening | What to do |
| ---------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| "Your HQ is unreachable" | The machine running your HQ is off, asleep, or not connected to the internet | Turn on or wake the machine running Dash and check its internet connection. The web client reconnects automatically once it's back. |
| "This HQ needs to be re-enrolled from Desktop before web access works" | This HQ was set up for remote access before web support existed, so it hasn't shared what it needs with the web client yet | Nothing to redo by hand: open Desktop on that computer once — it updates the HQ's app access automatically when it starts. Then come back and pick the HQ again. |
| "Your web session for this HQ was revoked. Pair again to continue." | This browser's access to the HQ was revoked — either by you from the Devices screen, or by someone else with access to the HQ | You're back at the HQ list. Pick the HQ again to reconnect. If you didn't revoke it yourself, check the Devices screen on your other clients for anything you don't recognize. |
| "No HQs linked to your account yet" | Your Dash account isn't linked to any HQ | In Desktop, open **Settings → Devices → Remote access** and enroll this machine. |
Revoking a browser's access stops it from reaching your agents immediately — if
that browser has a chat open, it disconnects there and then rather than at its
next request. It does not change any other device's access, and your
conversations stay exactly where they are.