Skip to content
Design System
GitHub

Settings

Sections beside their explanation; switches apply at once, fields collect into a save bar.

Overview

When to use

  • Account, site and fleet settings.
  • Any page of preferences.
  • Plan, usage and invoices, without taking payment details.

Use something else

  • Creating or editing one record: Form.

Blocks

Settings page

Sections beside their explanation; switches apply at once, text fields collect into a save bar that appears only when something changed; a danger zone that names the consequence.

Install
npx shadcn add @syncrobotic/settings-page

Notification matrix

Events by channel as checkboxes that apply at once; emergency stops are locked on and say so.

Install
npx shadcn add @syncrobotic/settings-notifications

API keys

Create, list and revoke API keys: a new secret shown once with a copy button, revoking confirmed first.

Install
npx shadcn add @syncrobotic/settings-api-keys

Plan and billing

Plan and renewal, robots and seats against what the plan includes, this period's usage, the card on file (brand and last four) and invoices with their PDFs; cancelling confirms first. No checkout or card form: those stay on your payment provider's pages.

Install
npx shadcn add @syncrobotic/settings-billing

Webhooks

Endpoints with their events and state, adding one with its signing secret shown once, test events, recent deliveries, rotating and deleting.

Install
npx shadcn add @syncrobotic/settings-webhooks

Signed-in browsers

Where you are signed in, as browsers: sign one out, or all the others after a confirmation; browsers that skip the 2FA code for 30 days.

Install
npx shadcn add @syncrobotic/settings-sessions

Usage rules

  • A switch applies at once; text fields wait for Save.
  • Say what a setting does next to it, not in a tooltip.
  • A secret (an API key, a signing secret) is shown once, with a copy button, and says it will not be shown again.
  • Signed-in sessions are browsers, never devices: a session is a browser's cookie.