Skip to content
Users and access

Users and access

PULSE keeps its own accounts in the users table. Each account has one role: admin, editor, or viewer. There are three ways an account comes to exist.

The break-glass admin

When PULSE_ADMIN_PASSWORD is set, the server creates or updates an account named admin with the admin role at every start. Change the username or email with PULSE_ADMIN_USERNAME and PULSE_ADMIN_EMAIL.

Without the variable, the log says No admin password injected (PULSE_ADMIN_PASSWORD/ADMIN_PASSWORD unset) — skipping admin seed; break-glass login unavailable until one is provided.

This is an emergency account. Give it a strong password from the secret store, and use Google sign-in and seeded roles for everyday access.

Google sign-in

Set GOOGLE_CLIENT_ID to turn on Sign in with Google, and set AUTH_ALLOWED_EMAILS to the people allowed to use it. Google sign-in fails closed:

SituationResult
GOOGLE_CLIENT_ID unsetNo Google button. The exchange endpoint answers google sign-in not configured (GOOGLE_CLIENT_ID unset).
Allowlist emptyNobody signs in with Google. The user sees google sign-in is not available on this instance.
Email not on the allowlistRefused with this account is not authorized for this instance.
First sign-in of an allowed emailA new viewer account with an unusable random password.
Email removed from the allowlist while signed inThe next request is refused with PermissionDenied (this account is no longer on this PULSE instance's sign-in allowlist), and /auth/refresh answers 403.

The allowlist is re-checked on every authenticated request (gRPC, HTTP routes, A2A, media) and on every refresh, not only at sign-in. Removing an address, or a TIDE add_users grant expiring, ends that person’s access at once instead of when their refresh token runs out. With no allowlist configured (a local, password-only run) there is nothing to re-check. The break-glass admin is exempt.

Set AUTH_GOOGLE_ONLY=true to hide the password form. The break-glass admin still exists, but the app no longer shows the form to reach it.

Seeded roles

AUTH_SEED_USERS grants roles by email, as a comma-separated list of email=persona pairs. Runink TIDE’s operator projects it from the ClientInstance’s user list. It is applied at every start, and it is the roster: it applies exactly, downwards as well as upwards.

PersonaRole
admin, org_admin, owneradmin
writer, editoreditor
reader, viewerviewer
  • A seeded email that has no account yet gets one with an unusable password, so that person signs in with Google.
  • A listed user whose persona is now lower is lowered to it.
  • An admin or editor the seed no longer lists, or lists with an unknown persona, is demoted to viewer (the log says Seeding: demoted …). Whether that person may still sign in at all is decided by AUTH_ALLOWED_EMAILS.
  • The break-glass admin (PULSE_ADMIN_EMAIL) is never raised, lowered or disabled by the seed.
  • If every entry is malformed, nobody is demoted and the log says AUTH_SEED_USERS is set but grants nothing PULSE recognises.

What each role may call

Every RPC has a minimum role. The gate runs in both the unary and the streaming interceptor and fails closed: a method with no entry is refused for everyone, admins included, and the build will not pass until it has one. The role comes from the caller’s users row (cached for at most 5 seconds), never from the token’s role claim, so a demotion takes effect within seconds even for a token that is still valid.

TierWhoCovers
publicanyone, before sign-inIdentityService/Login, ModelService/GetModelStatus
sessionany signed-in account, even one with no recognised roleIdentityService/GetCurrentUser, Logout
readviewer, editor, adminevery List* / Get* of your own records, the activity stream, exports, AuditPipelineService/GetAuditRun and ListAuditRuns, RadarService/ListDiscoveredChannels and ListTrendingPosts
writeeditor, admineverything that generates (spends model time) or changes data: all Generate*, ModelService/Complete, AuditPipelineService/RunAudit and ApplyAuditActions, live market research, lead create/scrape/outreach, PlaceAICall and SendOutreachEmail, campaign, content, publishing and integration changes
adminadminthe Admin page (AccessService) and the messaging contacts and carrier settings

A viewer can therefore read every page but cannot run an audit, generate, or approve. New Google accounts start as viewer (see above), so an admin or the seed must raise them before they can work.

Some write-tier calls have a stricter gate in their handler as well: ApplyAuditActions apply/commit/pr need an admin and PULSE_AUDIT_APPLY; PlaceAICall needs PULSE_OUTBOUND_CALLS and PULSE_AI_CALLS. See Publishing controls.

If the server cannot read the caller’s role, the call fails with Unavailable: RBAC: could not read your role, never with an allow.

The Admin page

Admin lives inside the Account page. There is no Admin entry in the navigation rail: an admin opens Account, which leads with Admin (the way into Members) and then Messaging. Someone who is not an admin of this instance sees neither section. Members itself is the shared Runink members page (runink.ui.access.v1.AccessService) at /admin: list members, invite, change a role, remove. The server reads the caller’s role fresh from the users table on every call, not from the token, and refuses anyone who is not an admin of this instance.

Billing is not under Account. Plan, seats and usage are on their own tab, Settings → Subscription; see Billing.

What a change does depends on where the roster lives:

DeploymentWhat happens to a change
PULSE may patch its own ClientInstance (PULSE_CLIENT_INSTANCE is set and the pod has permission)Written to the ClientInstance first, then to the users table. It is pending until the operator re-projects the roster and PULSE restarts.
AUTH_SEED_USERS is set, but PULSE cannot write the ClientInstanceRefused, with a sentence saying where access is changed. A local change would be undone at the next start.
NeitherThe users table is the roster. Changes apply at once.

When a role changes, PULSE ends that person’s sessions, so the new role takes effect at their next sign-in (the RBAC gate already applies it within seconds). PULSE keeps no seat roster, so invites are not limited by the number of seats on the subscription.

PULSE serves one instance per deployment. Its ID is PULSE_CLIENT_INSTANCE, else TENANT_ID, else pulse.

Sessions

Sessions live in the sealed app root, not in the database, so every replica sees the same state.

  • An access token lasts 24 hours. A refresh token lasts 7 days and works once. A session lasts at most 30 days.
  • Signing out revokes the session and every token issued in it.
  • The Account page can end all of a person’s sessions on every device. It also carries Appearance, the person’s own light or dark preference.

Tokens issued before server-side sessions existed carry no session ID and are refused. Those users sign in again once.