1.2. AlgaPSA Home Page: Quick Start Guide and Platform Features

Upon logging in, you'll be directed to the Home Page. This is the starting point for orienting a new MSP team before daily work begins in clients, tickets, time, projects, and billing.

The Home Page provides a Quick Start Guide for getting your MSP acquainted with Alga, highlighting key areas like adding your first client, setting up your team for time approvals, and inviting team members. It also showcases "Platform Features" such as Streamlined Ticket Management, Security Settings, Projects, and Scheduling.

Figure 1: AlgaPSA Home Page - Quick Start Guide and Platform Features overview

1. Review the Quick Start Guide first. For a new tenant, the most useful sequence is to add a first client, configure the team for time approvals, and invite team members.
2. Use the client setup item to create the first client record your team will work from. A client such as Harbor Clinic should be added before contacts, locations, tickets, and time entries are associated with that organization.
3. Use the time approval item to confirm the team process for reviewing submitted time sheets. This helps managers catch missing notes or incorrect service categories before the work reaches billing.
4. Use the invitation item to bring staff into the tenant and assign roles appropriate to their job, such as "Technician," "Dispatcher," "Manager," or "Finance."
5. Scan the "Platform Features" area to identify the next setup area for your role. A service manager may focus on Streamlined Ticket Management, while an administrator may start with Security Settings.

After reviewing the Home Page, you should know which onboarding tasks are still unfinished and which major product areas are available. If your team is still configuring the tenant, use the page as a checklist rather than jumping straight into daily operations.

Operational tip: after onboarding, revisit the Home Page with each role in mind. Dispatchers, billing admins, and technicians may notice different next steps, and that can reveal missing setup before a client-facing workflow depends on it.