tempkey
Start free

How Tempkey works

A contractor access lifecycle in four steps: connect tools, create a grant, let reminders run, then revoke and verify.

Start free

The four steps

  1. Connect tools

    Bring your own admin API credentials. Secrets are write-only in the browser and encrypted by the backend.

  2. Grant access

    Add the contractor, choose tools and permissions, and set 7/30/60/90-day access windows.

  3. Warn before expiry

    Notification scheduling is workspace-configurable so handoff happens before the clock hits zero.

  4. Revoke and verify

    Tempkey executes revocation, reads back provider state, and records append-only audit evidence.

Tempkey integrations screen: connecting a tool with a write-only token field beside a connection-status panel.
1. Connect tools — paste an admin token once; it's encrypted and never shown again.
Tempkey grant form: contractor name and email, a 30-day duration picker, and per-provider permission rows.
2. Grant access — pick the contractor, the tools, and the window.

One grant, every surface

A single contractor record tracks status per tool, so a partial revoke or a degraded connection is visible at a glance instead of buried in five admin consoles.

Extend without re-work

Contract running long? Extend a grant in one click and the expiry clock, reminders, and audit trail all move with it.

Built to be checked, not trusted

Every revoke action reads provider state back before marking a grant closed, so “done” means done, not “request sent.”

Tempkey dashboard showing one grant flagged 'Partly applied' beside healthy active and revoked grants.
3-4. Warn before expiry, then revoke and verify — a partial failure is flagged right on the dashboard, never silently marked done.
Fits the stack you already run.

10 providers are natively enforced, 2 more (Notion, and Trello) are tracked as limited-native, and Zapier/Make bridges cover the long tail as best-effort automations.

Browse integrations