FlowPSA Documentation
FlowPSA is the service desk, time, and billing record for teams that run FlowRMM. These guides explain how the product works and how operators use it day to day. They are public and written for people evaluating or running FlowPSA, not for developers of the product.
Every example uses the fictional Acme world: Acme MSP is the operator, Acme Corp is the client company, Acme HQ and Acme Warehouse are sites, and acme-wks-01 is an endpoint enrolled in FlowRMM. The same pattern fits an internal IT team that serves its own company.
Start here
- Get Started with FlowPSA: turn FlowPSA on beside FlowRMM and run one ticket from alert to draft invoice.
- How FlowPSA Works: the objects, who owns what, and the steps that always need a person.
- Plain-English Glossary: short definitions for every term in these guides.
The daily loop
- Intake. Email, the client portal, a FlowRMM escalation, or an MCP agent opens the ticket. See FlowRMM Integration.
- Dispatch. Operators take the next ticket by a published urgency score. See Smart Dispatch & Queues.
- Work. Tasks and change requests hang off the ticket. See Tickets, Tasks, Changes & Projects.
- Resolve. The ticket passes the gate. See The Resolution Gate.
- Bill. Approved time becomes a draft invoice. See Time & Timesheets and Agreements & Invoices.
What FlowPSA does not claim
FlowPSA does not send invoices on its own, does not let an agent approve a change or post an invoice, and does not run remote control or endpoint commands. FlowRMM owns endpoint execution. Quotes, stock, purchase orders, e-sign, and recurring invoices are on the roadmap and are not described here as available.