> For the complete documentation index, see [llms.txt](https://docs.alpha-security.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alpha-security.app/user-guide/web-ui.md). # Web UI The web interface is where you review captured evidence, explore the entity graph, manage findings, and generate reports. ## Layout The sidebar on the left is the main navigation: * **Dashboard** - Overview of the current engagement: recent runs, entity counts, activity * **Runs** - Timeline of all captured commands and their output * **Entities** - Browse hosts, services, credentials, and other parsed data * **Graph** - Interactive graph showing how hosts, credentials, and services connect * **Findings** - Finding board for tracking vulnerabilities * **Reports** - Generate and export reports * **Settings** - Engagement settings, collector tokens, operator management ## Runs view Shows every command captured by the collector, newest first. Click a run to see: * The exact command that was executed * Raw terminal output (with ANSI colors preserved) * Entities that were parsed from the output * Tags and metadata You can search across all raw output using full-text search. Even if Alpha doesn't have a parser for a tool, the raw output is stored and searchable. ## Entities view Entities are organized by kind: hosts, services, web endpoints, credentials, identities, shares. Each entity links back to the run(s) that discovered it. Entities are deduplicated within an engagement by their natural key. For example, if nmap and netexec both find port 445 on 10.0.0.5, they merge into one service entity with evidence from both runs. ## Admin panel Admins see an additional **Admin** section for managing operators (creating accounts, assigning roles, resetting passwords) and system settings. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.alpha-security.app/user-guide/web-ui.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.