Setup
Settings workspace
A visual guide to the DrowAI Settings page and its API, Network, System, Data Management, Display, and CVE subtabs.
Settings centralizes account-level and application-level configuration. Most operators should treat this page as a setup and administration area rather than part of the normal task execution workflow.
API
The API subtab manages provider-neutral LLM configuration and the Shodan API key. LLM provider settings control which models are available to chat and reporting features. Shodan configuration supports reconnaissance and OSINT operations when a valid key is provided.
Network
The Network subtab presents network-related configuration concepts such as container isolation, VPN integration, rate limiting, SSH port range, and maximum concurrent containers. In the current application these controls are presentation-oriented settings, so operators should not rely on this tab as the source of task-specific VPN setup. Configure task VPN from the task creation flow.
System
The System subtab summarizes operational status and keeps destructive maintenance affordances separate from ordinary configuration. Treat this page as administrative context, not as a place to manage individual task output.
Data Management
The Data Management subtab defines tenant-level lifecycle policy for generated report data. The visible retention setting controls how long historical generated reports are retained. Current reports are preserved by automatic retention, and users with the right permission can still delete reports manually.
Display
The Display subtab controls presentation preferences. The main setting is the timezone used for dates and times across the application.
CVE
The CVE subtab controls deployment-level CVE indexing behavior. It includes enable/disable, daily UTC sync schedule, live status, last successful sync, manual sync, cancellation of a running sync, and purge/reinstall of local CVE index data.
Public-safe handling
Settings screenshots can expose account identity, provider configuration, API-key state, retention policy, timezone, CVE indexing state, and deployment policy. Public documentation should use approved lab settings only and fully mask credentials or external service configuration before publication.