Sign-in, settings and developers
Getting in, and the settings that follow.
Start here
Start with the complete picture.
Preview the pieces, then open the connected journey.
The journey
Follow a complete task.
Getting in, the settings people change, and the keys and webhooks developers need.
- Sign in, and try a wrong password.
- Change a setting and see it saved.
- Create an API key, copy it once, and add a webhook.
States it handles
A key shown once, a webhook you retry, a setting that saves or says why it didn't, a wrong password.
Your application stays in charge.
The example keeps fictional accounts and keys in the page. Enforce authentication and authorization in your server.
Own the source
Add the kit, or start with a few pieces.
Every piece installs with the shadcn CLI and becomes source in your repo. Free pieces stay free; Pro unlocks the rest of every kit.
Add the whole kit
With Pro, after the one-time registry setup. One set of files for any components.json style, Base or Radix; the primitives run on Base UI.
pnpm dlx shadcn@latest add @notchset/sign-in @notchset/settings-layout @notchset-pro/api-key-list @notchset-pro/webhook-list @notchset/secret-reveal @notchset/switchStart with the free pieces
No account, no setup. One command for every shadcn style.
pnpm dlx shadcn@latest add https://notchset.dev/r/sign-in.json https://notchset.dev/r/settings-layout.json https://notchset.dev/r/secret-reveal.json https://notchset.dev/r/switch.jsonNew project? Set up your project. The full kit includes Pro pieces and uses your authorized registry setup.
6 live pieces