A PIN in front of your connected accounts

An optional PIN on the Integrations screen, enforced on the server routes that return credentials — not just on the tab that displays them.

What it is

Integrations is already admin-only, but role is a property of the account and not of whoever is currently sitting at the unlocked laptop. The PIN adds a second factor at the moment of access. Attempts are throttled and then locked out, and a forgotten PIN is reset by email to the requesting admin's own mailbox. The unlock is a signed, short-lived cookie bound to one user and one org.

Also called: second password · protect integrations · lock settings · someone used my laptop · extra security · second factor for credentials · lock my API keys · integration lock · integrations PIN · lock the API keys page

See it
A PIN in front of your connected accounts
Area
Platform & Admin
Group
Security & Compliance
System
Platform Trust
Solves
3 named problems
01Set an optional PIN on Settings → Integrations
02The server enforces it on the routes that return decrypted credentials, not just on the UI
03Failed attempts back off and then lock out
The Integrations tab showing the PIN prompt over the credential panel, with the lockout counter — integration-lock route + settings UI. Sample data — no customer information appears here.
How it works
  1. 1Set an optional PIN on Settings → Integrations
  2. 2The server enforces it on the routes that return decrypted credentials, not just on the UI
  3. 3Failed attempts back off and then lock out
  4. 4Reset goes to the requesting admin's own mailbox
  5. 5Unlock is a signed httpOnly cookie bound to one user and one org, expiring on its own
Why we built it

Admin-only is a property of the account, not of the person sitting in front of it. An unlocked laptop on a trailer desk, or a session left open on a shared office machine, exposes every service the business has connected — the payment processor, the CRM, the estimating system. An optional PIN now stands in front of that screen, enforced where the credentials are actually handed out rather than merely hiding the tab, because a PIN that only hides a tab is theatre. Attempts back off and then lock out so a short code cannot be guessed in a minute, and a reset goes to the requesting admin's own mailbox — if being logged in were enough to clear it, it would protect nothing against the exact situation it exists for.

The problem
  • An unlocked session exposes every connected service a business has
  • UI-only locks are bypassed by calling the API directly
  • A PIN clearable from an active session protects nothing
Sound familiar?
What you get
A borrowed or unattended session cannot reach connected-account credentials
Brute force is throttled and locked out
The unlock expires on its own instead of lasting as long as the login

See it on your own jobs

Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.

or keep browsing features →