Skip to content

Accounts & devices

Each account belongs to exactly one organization. Employees see only their own records; administrators see their whole organization and can also record their own time. Every employee belongs to one group, or uses the organization’s default group if none is assigned — groups are for organizing people and confer no management privileges of their own. Platform-staff access (for support purposes) is separate from organization accounts, controlled and audited.

Administrators invite people individually by email. There is no public sign-up.

  • An invitation is a single-use link valid for 7 days.
  • Sending invitations (initial sends and resends) is capped on a rolling 15-minute window: 3 per address, 20 per IP, 100 globally. These caps throttle sending; they never lock an account.
  • Completing the passwordless invitation link only proves access to that mailbox at that moment. Vespi never provisions, merges, or rebinds an account because an email address matches an existing one — identity is bound by the authentication provider’s issuer and subject together, not by email.
  • The web portal uses server-side sessions with secure, HttpOnly cookies and CSRF protection.
  • The Android app uses a separate native OIDC/PKCE client, distinct from the web login.
  • A web session has a 30-minute idle timeout — this is an inactivity limit, not a maximum session lifetime; an actively used session can continue beyond 30 minutes.
  • If an administrator deactivates someone’s sign-in provider access, that blocks new sign-ins immediately. It does not retroactively invalidate an already-open web session on a per-request basis — ending an active session requires revoking the account or membership directly.

There is no self-service mailbox change or account recovery. If an employee loses access, an administrator assists and the action is audited. Recovering a sole remaining administrator account requires support to independently verify organizational authority, and the action is audited and existing contacts are notified.

Organizations are protected against accidentally locking themselves out: the last active administrator in an organization cannot be revoked or demoted. Access and privilege changes are recorded with an audit entry capturing who made the change and why.

  • The first device registration for an account proves possession of a private key generated on that phone (a P-256 keypair held in the Android Keystore) — enrollment or a device identifier alone is never enough to authorize clock actions.
  • Replacing a registered phone requires administrator approval. Approving a replacement revokes the old phone’s ability to act and preserves its history — the old device record is deactivated, never deleted, so its evidence (including any late-arriving evidence from it) stays available for review.
  • Native API access uses narrow, purpose-specific scopes: reading organization/tenant data requires one scope, enrolling a device requires another, and recording time requires a third plus a one-time, 60-second-lived cryptographic challenge bound to the specific organization, user, device, action and idempotency key. A device that only holds the enrollment scope cannot record time.