22.1. Install AlgaPSA Mobile and Sign In

Set up the phone before dispatching a technician to a client site. A service manager can use one test ticket to check sign-in, access, and notifications, so the technician arrives at GreenLeaf Dental Group with the right queue already available.

This guide covers AlgaPSA Mobile 1.6.1 for iOS and Android. The app is for internal MSP users. Client portal accounts cannot sign in.

Before you start

Have an internal AlgaPSA account, permission to view the tickets you will work, and an internet connection to your AlgaPSA server. Ask your service manager for the server address if your MSP uses a self-hosted installation or AlgaPSA Appliance. Use your normal workplace sign-in method.

The app needs connectivity to load records and save work. A saved comment draft is not confirmation that a ticket update reached the server.

Install and connect

1. Install AlgaPSA Mobile from the Apple App Store or Google Play.
2. Open the app. For an Alga Cloud account, continue from Sign in.
3. For your own server, tap Change server. On Server, enter the Server address, such as helpdesk.example.com, and tap Connect. A hostname without a scheme uses HTTPS; the distributed app requires an HTTPS server.
4. Alternatively, use Scan QR code to scan the Connect this server QR code supplied by your AlgaPSA dashboard. Allow camera access, review the address filled into the field, and tap Connect. Scanning fills in the address; you still confirm the connection.
5. To return to the hosted service, choose Use Alga Cloud on the Server screen.

The app checks the address before saving it. If it cannot reach the server, confirm the hostname and the phone's network connection. A server that does not support mobile sign-in must be updated or checked by the administrator.

Sign in with your workplace account

1. Tap Sign in. The app opens the server's sign-in page in the system browser.
2. For password login, enter Email and Password, then choose Sign in on that page. Complete any additional verification requested by your account.
3. For SSO, use your organization's Microsoft or Google sign-in option on the browser page. These are the providers the mobile sign-in support check recognizes. Provider setup belongs to the administrator.
4. Finish the browser flow and return to AlgaPSA Mobile. Open a ticket you expect to work and confirm the client and assignment.

The email and password fields are on the browser sign-in page, not a separate native form in the app. An SSO-not-configured message does not by itself prevent password login.

On supported Apple devices, Sign in with Apple is also available. It must be connected to your AlgaPSA account. You can sign in normally first, then use Settings > Security > Sign in with Apple to connect the Apple ID. If Apple sign-in reports that no account is linked, follow the prompt to complete your normal workspace login. Confirm the account shown in Settings before using it for field work.

Turn on biometric lock

1. Set up biometrics on the phone itself.
2. Open the app's menu and choose Settings.
3. Under Security, tap Biometric lock and complete the device's authentication prompt.
4. Check that the value changes to On.

The app requests an unlock when opening a saved signed-in session and when returning after its unlock grace period. If it says Biometrics are not set up on this device, finish the phone's biometric setup before trying again. Biometric lock does not create a different AlgaPSA account or change its permissions.

Register and test push notifications

1. In Settings > Notifications, turn on Push Notifications.
2. Allow notifications in the phone's permission prompt. If access was denied earlier, use Open Settings from the app's notification warning and allow it in the device settings.
3. Review Push me for. Choose All notifications, Normal and high priority, or High priority only. These are notification priorities from AlgaPSA notification settings, not the priority filter on the ticket list.
4. Under Security, review Hide sensitive notifications if client details should be hidden in future push notifications.
5. Tap Send test notification in Notifications. Read the result and check the phone's notifications. The test targets this account's registered devices, so more than one device may receive it.

Registration is tied to the server and account. The app checks registration at launch and resume and renews it after a day, allowing a subsequent check to repair a server-side registration reset. Sign-out and host changes clear the local registration record.

For self-hosted delivery requirements, including the server's outbound connection to exp.host, see 18.1. Self-Hosting AlgaPSA: The On-Premise Appliance.

Choose appearance and check the tenant theme

In Settings > Appearance, tap the Appearance row to cycle through the choices:

The Theme row shows the tenant's theme name, or Custom for a custom pair. The administrator chooses the pair in AlgaPSA settings; this row is informational. Mobile uses the server's preset or custom pair, including in the comment editor. The high-contrast pair uses stronger borders.

The app remembers your appearance choice and caches the tenant pair for later launches. Changes made by the administrator are picked up on a subsequent refresh, including when you return to the app or pull to refresh Settings. A server without theme information uses the built-in Alga appearance and shows Default. For administrator setup, see 10.21. Set Interface Themes, Dark Mode, and White-Label Branding.

Language

Version 1.6.1 provides the mobile interface in English and has no language selector in Settings. Language choices in the web app do not add translated mobile screens.

Sign out or switch servers

1. Open Settings > Account, choose Sign out, and confirm Sign out.
2. To change hosts, use Change server on the sign-in screen, enter the new address, and tap Connect. Use Use Alga Cloud to return to the hosted service.
3. Sign in to the new server and verify the account and tenant shown under Account, and Base URL under About in Settings.
4. Check push permission and run Send test notification for the new account.

Sign-out attempts to unregister the phone from the previous server and ends the local session. Switching hosts clears the signed-in session, local push-registration record, and cached tenant theme. Complete this check before handing a phone to another technician.

Service manager rollout check

On each issued phone, verify the version beside AlgaPSA Mobile under Settings > About, open the assigned ticket, send a test notification, and confirm the technician can save the kind of work they need to perform. Start with 22.2. Work Tickets from the Phone, then use 22.5. Your Queue: Activities on the Phone to review the day's mixed workload.