# SaaS Screens (Lumen Halo): prompt.md (v1.0.0)

- id: `lumen-saas-screens` · version 1.0.0 · block · pro (All-Access)
- category: App screens
- build: Base UI (one set of files; its dependencies follow the build)
- install (this build): `npx shadcn@latest add @beautiful-ui-pro/lumen-saas-screens`
- npm dependencies: none
- registry dependencies: utils, @beautiful-ui/lumen-avatar, @beautiful-ui/lumen-badge, @beautiful-ui/lumen-button, @beautiful-ui/lumen-card, @beautiful-ui/lumen-dialog, @beautiful-ui/lumen-field, @beautiful-ui/lumen-input, @beautiful-ui/lumen-native-select, @beautiful-ui/lumen-progress, @beautiful-ui/lumen-switch, @beautiful-ui/lumen-table, https://beautiful-ui.dev/r/lumen-foundation.json
- docs: https://beautiful-ui.dev/components/lumen-saas-screens
- The install command carries everything this item needs (files, CSS, tokens, npm and registry dependencies). Prefer it to copying source by hand.

The workspace screens a SaaS app needs next to its analytics: Team (members, roles, invites, remove with a confirm), Billing (plan, seats, usage meters, invoices) and Settings (workspace, notifications, and a danger zone that asks you to type the name). Every async action shows that it's working and says when it fails.

## Build it
- Stack: React 19 (`ref` is a plain prop), TypeScript, Tailwind CSS v4 utilities, a shadcn-initialised project with the `@/*` alias.
- Packages: none beyond React.
- Files: `components/ui/lumen/workspaces/saas-screens.tsx`.
- Registry dependencies, installed with it automatically: shadcn `utils` (cn), `lumen-avatar`, `lumen-badge`, `lumen-button`, `lumen-card`, `lumen-dialog`, `lumen-field`, `lumen-input`, `lumen-native-select`, `lumen-progress`, `lumen-switch`, `lumen-table`, `lumen-foundation`.
- Builds: one set of files for both, but its dependencies come in Base UI and Radix builds. Install the one that matches the project (see Install): a free item's bare URL installs the Base UI build of it and its dependencies.
- Exports to keep: `TeamView`, `BillingView`, `SettingsView`, and every exported type.
- CSS: the install merges this item's rules (the registry `css` field) into your global stylesheet, in `@layer components`, and adds the lumen foundation (tokens, keyframes, motion levels) once. Nothing to import by hand.
- Re-running `add` (or `--overwrite`) re-applies those rules: put overrides in your own CSS, never in the installed rules.
- Tokens: retheme with the `--lumen-*` custom properties (`--lumen-accent`, `--lumen-accent-text`, `--lumen-bad`, `--lumen-bad-text`, `--lumen-focus`, `--lumen-good`, `--lumen-good-text`, `--lumen-hairline`, `--lumen-ink`, `--lumen-muted-ink`, `--lumen-series-1`, `--lumen-series-2`, `--lumen-series-3`, `--lumen-series-4`, `--lumen-series-5`, `--lumen-series-6`, `--lumen-warn`, `--lumen-warn-text`); this item's CSS also reads `--lumen-font-mono`, `--lumen-font-sans`, `--lumen-radius-k`. Never add Tailwind colour classes inside the component.

```tsx
import { TeamView, BillingView, SettingsView } from "@/components/ui/lumen/workspaces/saas-screens";
```

## Parts

| Part | data-slot | What it is for |
|---|---|---|
| `TeamView` | — | Members, roles and invites. |
| `BillingView` | — | Plan, usage and invoices. |
| `SettingsView` | — | Workspace settings and the danger zone. |

## Sound
- Keep every `data-slot` and `data-sound` attribute: the sound layer reads them.
- Installing this item adds no audio. Nothing plays until the app mounts `GlassSoundProvider` once (install: `npx shadcn@latest add https://beautiful-ui.dev/r/glass-sound.json`, import from `@/components/beautiful-ui/glass-sound`); `GlassSoundToggle` is its mute control. Without a provider the audio engine never loads.

## Match the original
- Read `components/ui/lumen/workspaces/saas-screens.tsx` as the reference implementation before changing or recreating anything, and match it: sizes, colours per theme, motion timings, copy and behaviour.
- If you deviate (a prop you can't honour, a style you changed, a dependency you swapped), say so in your reply, part by part.
- Keep the accessibility contract, the keyboard map and the motion levels listed below.

## Use it when
- team settings page, members and roles, invite users, billing page, usage limits, invoices, workspace settings, delete workspace, SaaS starter, Lumen
- A SaaS app's account screens, in the same material as its dashboards
- A starting point you wire to your own backend through callbacks

### Not when
- Checkout itself: use your payment provider's hosted checkout

## Mistakes
- Check permissions on your server: the UI hides owner-only actions, it doesn't secure them
- Pass real seat counts so Invite is disabled when full

## Usage

```tsx
import { TeamView, BillingView, SettingsView } from "@/components/ui/lumen/workspaces/saas-screens";

<TeamView members={members} onInvite={(email, role) => api.invite(email, role)} onRemove={(m) => api.remove(m.id)} seats={10} />
```

## Props

| Prop | Type | Default | What it does |
|---|---|---|---|
| `TeamView members / onInvite / onRoleChange / onRemove / seats` | `Member[] / async callbacks / number` |  | People, roles and invites. Throw from a callback to show its error. |
| `BillingView plan / seats / usage / invoices / onChangePlan / onManagePayment` | `…` |  | The plan card, usage meters (a warning at 80%) and the invoice list. |
| `SettingsView defaultValue / onSave / onDelete` | `WorkspaceSettings / async callbacks` |  | Workspace name, time zone and notifications; delete asks you to type the name. |

Full docs: https://beautiful-ui.dev/components/lumen-saas-screens

## Customising
- Colours: set the `--lumen-*` tokens on `:root`, or on a container with the `lumen-scope` class to retheme one area. Add the `lumen-inherit` class to follow your shadcn palette instead (`--chart-N`, `--destructive`).
- Dark mode follows the `.dark` class on an ancestor (the shadcn and next-themes convention).
- Update later by re-running the install with `--overwrite` (review the diff if you edited it). Changelog: https://beautiful-ui.dev/r/changelog.json

## Keyboard

| Keys | Action |
|---|---|
| Tab / Enter | Move and act |
| Escape | Close a dialog |

## Motion inventory

| Interaction | What moves |
|---|---|
| Dialogs | Lumen Dialog's spring |

## Accessibility contract (preserve when editing)
- Each screen is a labelled region with one heading
- Role pickers name the person; destructive actions confirm in a dialog
- Errors and saves are said in words (role=alert, aria-live)

## Install

```bash
npx shadcn@latest add @beautiful-ui-pro/lumen-saas-screens
```

Pro item: needs the `@beautiful-ui-pro` registry in `components.json` and `BEAUTIFUL_UI_TOKEN` in `.env.local` (https://beautiful-ui.dev/account). Setup: https://beautiful-ui.dev/docs/pro. Your components.json `style` picks the build: radix-*, new-york and default get Radix, base-* gets Base UI.

## Credits
- Built on shadcn/ui (https://ui.shadcn.com)

The lumen foundation (the tokens listed above, keyframes and motion levels) installs once with the first component; its CSS is public at https://beautiful-ui.dev/r/lumen-foundation.json.