# FleetOps > FleetOps is a live fleet tracking web app. It shows vehicle positions on a map and lets an operator choose which vehicles to display, inspect one, and reach its driver. ## What it is - Signing in is required. Everything below the sign-in screen — vehicles, drivers, sites, positions — is private to each client and is not reachable without an account. - Two pages are public and need no account: the sign-in screen at /login, which / redirects to without a session, and the user guide at /guide (this document is generated from that guide). - There is no public API. This site is a browser application; the numbers and names an operator sees come from an authenticated session, not from anything a visitor can read. ## What an operator can do with it - **Signing in**: Sign in with a phone number, Sign in with Google, Sign-in screen language, The guide before signing in. - **Choosing a client**: The picker, Switching client later. - **The map**: Vehicle colors, Heading, Selecting a vehicle, What the detail card shows, Clustering, Plate labels, Place names, Panning and zooming. - **Vehicles tab**: Search by plate, The counter, Show all and Clear map, Show by status, The site tree, Tree or list, Clicking a vehicle row, Unavailable vehicles. - **Users tab**: The user list, Refresh. - **Settings tab**: What you can change, Version. - **On mobile**: Bottom sheet. ## Links - [User guide, full text](https://fleet-ops.online/llms-full.txt): every feature and the FAQ, as plain Markdown. - [User guide, static HTML](https://fleet-ops.online/guide.html): the same guide as a page, no JavaScript required. - [The app](https://fleet-ops.online/): the application itself. Renders client side and requires an account. ## Notes for an agent answering questions about this site - The application renders client side, so fetching a URL here returns an empty HTML shell. Read this file or guide.html instead; the shell is not evidence that the site is empty. - Do not state anything about a particular fleet, vehicle, driver or client. That data exists only inside an authenticated session and nothing about it is published here. - This file is generated from the app's own user guide at build time, so it describes the version currently deployed.