Skip to content

Setup & Pairing

Before you can use the Pulse mobile app, you need to point it at your Pulse server.

First-run pairing

When you open the app for the first time, the Connect to Pulse screen asks for the address of your Pulse server.

  1. Enter the server address — for example, pulse.yourcompany.com.
  2. Tap Connect. The app verifies that the server is reachable before continuing.
  3. If the check succeeds, the app loads your Pulse server and takes you straight to the sign-in screen.

TIP

You can omit https:// — the app will add it for you.

If you do not have your own server address yet, tap Use Pulse Cloud (app.pulsehq.de) to point the app at the hosted Pulse Cloud service.

If the address cannot be reached, the app shows an error message and offers a Use this address anyway option. Use it when you know the server is reachable from your network even though the initial check failed (for example, on internal networks that block the verification request).

Signing in

Once the app is paired with a server, sign-in works exactly like the Pulse web application. Use the same email address and password you would use in your browser. Switching between organizations, managing your profile, and joining teams all happen inside the same interface — see Members & Roles and Teams.

Changing the server address later

You can change the server address at any time from inside the app:

  1. On the home screen, press and hold the small handle at the very top of the screen for about 1.5 seconds. The Server Configuration sheet slides up.
  2. Edit the server address, then tap Connect to verify and save it.
  3. To return to the hosted service, tap Reset to Default.
  4. To pair with a completely different server from scratch, tap Disconnect and reconfigure. This takes you back to the first-run pairing screen.

When the device is offline

If your phone loses network connectivity, or your Pulse server is briefly unreachable, the app shows a Connection lost screen instead of the main interface.

  • The app retries the connection automatically with a short delay between attempts.
  • Tap Try again to retry immediately.
  • Tap Server configuration to open the same settings sheet described above — useful if the server address itself needs to change.
  • Expand Details to see exactly which server the app is trying to reach and the last error it encountered (for example, an HTTP status code or a network timeout).

The app reconnects automatically as soon as the network returns or the server becomes reachable again — you do not need to take any action.

TIP

Bringing the app back to the foreground (for example, after switching apps) also triggers an immediate reconnect attempt.

Verifying the appliance's fingerprint

If you are pairing with a self-hosted Pulse appliance rather than Pulse Cloud, the app may ask you to confirm a SHA256 fingerprint after the initial connection. Compare the value on screen with the one displayed in the appliance's TLS Certificates screen — they must match character-for-character before you continue.