/
Foundations
Components
Blocks
Pages
Screens
Library
Playground
Grab Pro Now
Customize your admin
Grab Pro Now
Customize your admin
8 cards in the Productivity domain — same language, same primitives, ready to compose.
A share modal: e-mail chips + role picker land invitees as animated member rows, per-member role menus with remove access, and a general-access band.
4 PROJECT MEMBERS
Mara Ellison
m.ellison84@gmail.com
Theo Brandt
theo.brandt@gmail.com
Ines Novak
ines.novak91@yahoo.com
Ruben Ortiz
ruben.o_92@gmail.com
GENERAL ACCESS
View-only access for anyone with the link
The third CRM card: who can see which record, and which layer decided. Access is not a setting — it is computed per record by layering profile (a ceiling), record owner, org-wide default, role hierarchy, sharing rules and team shares, where the most permissive layer wins and only field-level security subtracts. Pick a person and a record and the stack resolves live: a VP cannot see a CS rep's case, peer AEs cannot see each other's private deals, and an SDR reaches a deal only through the opportunity team — still capped to read, with the amount masked.
Access isn't a setting — it's computed per record. The most permissive layer wins.
The companion to CRM workflows: that card shows how the process runs, this one shows how the records connect. The schema walks itself — from one Account out to 4 contacts, 2 opportunities, 1 quote, 3 cases and 37 activities — and the five relationship shapes every CRM is built from are selectable: 1:N, N:M through a junction object of its own, polymorphic, self-referencing, and the one-way Lead conversion. Object totals reconcile with the workflows card, and each object names the workflow steps that touch it.
Seven objects, five relationship shapes — and what one record reaches.
The Account is the hub: almost everything hangs off it. The two shapes people miss are N:M, which needs a junction object of its own, and poly, where one field points at several object types.
What a standard CRM actually runs, as one revenue lifecycle instead of a feature list: capture & route, score & qualify, convert, pipeline, cadence & SLA, quote & approve, handoff & cases, renew & expand. The spine carries each step's volume so the funnel visibly narrows; selecting a step plays that workflow's own animation and names its trigger, the records it writes, the role that owns it, and the rule the CRM fires automatically. Left alone it tours all eight.
The eight things a standard CRM runs, in the order they happen.
Every inbound lead lands in one place, gets checked for duplicates, and is assigned an owner before anyone touches it.
A task list: subtask clicks advance progress, Mark as all done completes every card, Add Task prepends a row, and the toolbar sorts and filters the live list.
Fix stuck transaction status on delayed card captures
Audit onboarding illustrations for design-system drift
Add voice-note comments to task threads
Scrub a UTC hour across SF, NYC, São Paulo and London: each row's working-hours heatline tints its local readout live, the footer narrates the overlap, and Find best time springs the scrubber to the one hour that works everywhere.
A personal knowledge base drawn as a live signal field: twelve intake sources fan through capture and process lanes into ten shelves and eight outputs, ~200 connections carrying travelling light on a canvas. Hover an intake family and the field dims to only the signals it feeds.
Everything you save, on its way to something you ship.
An assistant's history threaded on one curved rail: hovering a row moves the lit head to it, a comet tail lights the segment behind the direction of travel, and Day / Week / Month regroups the same pool while the rail re-threads around the new markers.