Concept spec

Atlas Jump: a command palette for Atlas CRM

One keystroke to reach any account, contact, deal, or action. A proposal to collapse Atlas's six navigation surfaces into a single keyboard-first jump box.

Designer
R. Vasquez
Date
Aug 28, 2026
Status
Draft for review
Target release
v4.2 (Oct)
01

Summary

Power users lose an average of 41 seconds per task navigating Atlas's sidebar, global search, and record tabs. Atlas Jump is a command palette, opened with ⌘K, that unifies record lookup and quick actions behind one fuzzy-search field. Every destructive action previews before it runs and every mutation is undoable from a toast, so speed never costs safety.

Goals

  • Reach any record in under 3 keystrokes plus enter
  • Run the 12 most common actions without leaving the keyboard
  • Make every palette-run mutation undoable for 8 seconds

Non-goals

  • Replacing the sidebar or record tabs in this release
  • Natural-language querying or AI-composed actions
  • Bulk operations across more than 25 records
02

The concept

Fig 1Palette opens centered over the dimmed workspace. Top match is preselected; enter jumps straight to it.

03

How it works

Trigger to undo in five steps

1

Trigger

⌘K (or Ctrl K) opens the palette from any Atlas screen. The workspace dims; focus lands in the search field with prior context preserved underneath.

2

Search

Fuzzy match across accounts, contacts, deals, and actions as you type. Results rank by recency and ownership; top match is always preselected.

3

Preview

Tab on a result reveals its action list; destructive or multi-record actions expand an inline confirm pane showing exactly what will change.

4

Execute

runs it. Navigation jumps immediately; mutations run optimistically and the palette closes so the user sees the result in context.

5

Undo toast

Every mutation surfaces a toast for 8 seconds with a single-click Undo. ⌘Z while the toast is visible reverts without touching the mouse.

04

Key states

EmptySuggests query shapes instead of a dead end.
ResultsRecords and actions interleave in one ranked list.
ConfirmInline confirm for destructive actions, then the undo toast.
05

Component inventory

ComponentPurposeStatesReuse
JumpOverlay Dim layer + focus trap that hosts the palette above any screen open, closing NEW
SearchField Query input with glyph, ghost placeholder, and escape hint empty, typing, loading NEW
ResultRow One record or action: type icon, name, kind tag, shortcut hint default, active, disabled NEW
ConfirmPane Inline summary of what an action will change, with cancel/confirm default, running NEW
UndoToast Post-mutation receipt with an 8-second undo affordance visible, undoing, expired EXISTING
KbdHint Keycap chip used in the footer strip and row shortcut hints default EXISTING
06

Interaction & motion

Keyboard map ⌘K open/close · move · run · Tab actions · Esc back, then close · ⌘Z undo while toast shows
Focus behavior Focus is trapped in the palette while open. On close, focus returns to the element that had it before the trigger; after a jump, it lands on the destination page heading.
Entrance / exit Palette scales 0.98 to 1 and fades in over 120ms ease-out; dim layer fades over 160ms. Exit reverses at 100ms. No spring, no bounce.
Reduced motion Under prefers-reduced-motion, all transforms are dropped and fades cap at 80ms.
07

Accessibility

08

Open questions

Q1

Can the search index return in under 80ms at p95?

The interaction model assumes results render within one animation frame of typing. If the current index can't hit 80ms p95 for tenants over 200k records, we need a local cache layer scoped to recents.

needs: platform eng
Q2

Do palette actions inherit page-level permissions as-is?

Some actions (merge, reassign owner) are gated per-view today. The palette is viewless, so we need a ruling on whether it checks record-level permissions directly or hides gated actions entirely.

needs: security review
Q3

Ship ⌘K knowing Firefox reserves it for the address bar?

We can intercept it on focused app pages, but not on first load before hydration. Proposal: keep ⌘K primary and document ⌘J as the fallback binding. Needs a call.

needs: product (M. Chen)