Get Started with FlowPSA
This walkthrough follows Acme MSP turning on FlowPSA beside its existing FlowRMM, then running one ticket for client Acme Corp from alert to draft invoice. An internal IT team follows the same path with its own company as the client.
Before you begin
- A running FlowRMM tenant with at least one enrolled endpoint, for example
acme-wks-01at Acme HQ. - An Azure environment where FlowPSA can run as a Container App next to FlowRMM, using the same Postgres in its own
flowpsaschema. - A Microsoft Entra administrator who can create the FlowPSA app registration and role groups. See Identity, Roles & Access.
Setup is self-serve by default. FlowDevs offers optional concierge setup as a service; it is never required to license FlowPSA.
1. Deploy and sign in
Deploy FlowPSA with its own runtime identity. That identity writes only the FlowPSA schema and reads FlowRMM clients, sites, and devices through views. Then configure Microsoft sign-in and assign yourself to the FlowPSA Admin role group.
After signing in, open Settings and check Sign-in & Access. It shows your verified tenant, your effective role, your queues, and a setup checklist that includes the FlowRMM connection.
2. Connect FlowRMM
In FlowRMM, an administrator enables PSA integration and configures the flow_psa provider with the FlowPSA address and a dedicated integration identity. Verify the connection before making FlowPSA the default for new escalations, and keep any previous PSA connection until the new path is verified. Details are in FlowRMM Integration.
Inventory sync maps FlowRMM client Acme Corp to a FlowPSA company by ID. There is no mapping spreadsheet.
3. Set up queues and a governance profile
Create queues for the skill groups you actually have, such as Service desk, Networking, and Security, and pick the Entra groups that work each one. Then choose a governance profile: Balanced MSP is the default. See Governance Profiles.
4. Add an agreement for Acme Corp
Open Companies, select Acme Corp, and add a labor agreement: included minutes per month, hourly rate after that, and a billing increment. See Agreements & Invoices.
5. Run your first ticket
- When FlowRMM escalates an alert on
acme-wks-01, FlowPSA opens a ticket linked to Acme Corp, Acme HQ, and the endpoint. - Press
cin the queue, or use Take next ticket, to claim it. The Omni-Timer starts. - Open FlowRMM from the ticket sidebar, help the user in a Remote Console session, and run the fix as an approved FlowRMM action. Attach the session and action to the ticket.
- Resolve. The resolution gate checks tasks, changes, knowledge, and endpoint proof.
- Stop the timer and save the time entry.
6. Approve time and draft the invoice
At the end of the week, submit your timesheet. A Billing user approves it. Then preview and create the invoice draft for Acme Corp. Posting it requires a Billing or Admin user who is not the person who requested it.
Next steps
- Connect your model over MCP: MCP & AI Agents.
- Give Acme Corp staff portal access: Client Portal.
- Learn the keys: Keyboard Shortcuts.
Related guides
Want hands-on help? Book a demo or get in touch.