Settings
Settings admins
The Admins settings pane where space owners invite people by email and manage the list of everyone who currently holds full permissions.
Available
Ports as-is
Examples
Rendered live from the maintained Storybook story. Lantern stores only the story id and embeds Storybook rather than duplicating the component or its demo.
Settings admins
Rendered live from Storybook
Storybook must be running for this to load — bun run start:storybook from the monorepo root, or set NEXT_PUBLIC_STORYBOOK_URL to a deployed instance.
Props
The component's public API, read from its TypeScript source. Descriptions come from TSDoc on the prop, so this table cannot drift from the component.
| Prop | Type | Default | Description |
|---|---|---|---|
admins | SettingsAdmin[] | [] | Undocumented — add TSDoc to the prop in the library. |
onInvite | (email: string) => void | — | Fired with the trimmed email from the invite field. Validation, dedupe and the resulting toast belong to the caller — this pane does not mutate the list it was handed. |
onRemove | (admin: SettingsAdmin) => void | — | Fired on confirming the removal dialog. |
initialEmail | string | "" | Seeds the invite field. |
initialPage | number | 0 | Zero-based page. Seeds the pagination. |
pageSize | number | 20 | Undocumented — add TSDoc to the prop in the library. |
initialRemoveTargetId | string | — | Opens the removal dialog on mount for the admin with this id — makes it a static story. |
className | string | — | Undocumented — add TSDoc to the prop in the library. |
Reference
Transcribed from the component audit. If this disagrees with the source, the source is right.
- Source
src/components/settings/SettingsAdmins.tsx- Portability
- Copies across unchanged — only the utils import path moves.
- Variants
status: active | pending- Notes
- Use it as the Admins tab of a space's settings sheet, above a paginated table with per-row status badges and a removal confirmation dialog. The owner's row never shows a menu since ownership can't be revoked, and invite validation, dedupe, and any resulting toast are left to the caller.