Skip to content

Signing in

PULSE has two ways in: Sign in with Google, and a username and password. Your PULSE shows the ones its administrator turned on.

Username and password

Sign in with your username, not your email address. A wrong username or password, or an account that has no password (accounts made through Google sign-in have none), answers invalid credentials.

Sign in with Google

The button appears only when your PULSE has Google sign-in set up. In a browser it is Google’s own button, as wide as the sign-in form; when your browser is already signed in to Google it names your account. PULSE never signs you in by itself when the page opens, so Sign out keeps you out.

Your Google address must be on your PULSE’s list of allowed addresses. The first time you sign in with Google, PULSE makes you an account with the viewer role, unless an administrator gave your address a role in advance.

When Google sign-in does not let you in, the sign-in form says why in your language, for example:

What you seeWhat to do
Your address is not on this PULSE’s list of people allowed to sign inAsk your PULSE admin to add it.
Nobody can sign in with Google on this PULSE yetThe allowed list is empty; ask your PULSE admin to add you.
Your Google account’s email address is not verifiedVerify it with Google, then try again.
Google sign-in is not set up on this PULSEUse your username and password.
This copy of the app is not registered with Google yet (Android)Use your username and password, or PULSE in your browser. Your administrator registers the app with Google.
Google sign-in is not available in this app on this device (Linux desktop)Use your username and password, or PULSE in your browser.

Closing Google’s window or sheet without choosing an account shows nothing.

What your role lets you do

RoleWhat it can do
ViewerRead everything in your account. Cannot start a check-up, send, call or publish.
EditorEverything a viewer can, plus run check-ups, make and approve content, send email and place AI calls (where your administrator allows them).
AdminEverything, plus Admin (members and roles) and the messaging settings, reached from Settings → Account.

Ask an administrator to change your role. The server checks your role on every action, so a button you can see is not a promise that the action is allowed. Administrators: see Users and access.

How long you stay signed in

  • In a browser, you stay signed in for up to 24 hours, then sign in again. The browser never holds your sign-in where a page script could read it.
  • In the Android or Linux app, the app renews your sign-in by itself for up to 30 days. It keeps it in the device’s secure store, never in a plain file.

Sign out is at the foot of the navigation rail. It ends that sign-in everywhere it is used at once. To delete your account instead, see Delete your account.

Where the session lives

For administrators and developers.

ClientWhat it holdsWhere
Android, LinuxAn access token (24 hours) and a single-use refresh token (7 days), sent as authorization: Bearer …The platform keystore. There is no plaintext fallback: if the keystore refuses the write, the session lasts only until the app closes.
WebNothingThe backend sets __Host-pulse_session, an HttpOnly, Secure, SameSite=Strict cookie scoped to the exact host. The sign-in response carries no token, and no refresh token is issued.

A cookie-authenticated call must also carry the header x-pulse-csrf: 1 and an Origin the server trusts: its own host, PULSE_PUBLIC_BASE_URL, or an exact entry of CORS_ALLOWED_ORIGINS (never a wildcard). The session behind the tokens lasts at most 30 days. See also Users and access, the HTTP endpoints, and, for the Android app, Google Play release.