Measured entry

hextaui-settings-team-members

teamminimal-flat

A client-side React settings card for listing members, showing roles and status, inviting people, changing access, transferring ownership, and removing users through supplied callbacks. It ships as a shadcn registry block and expects Tailwind theme classes, the local cn utility, Lucide icons, and a broad set of shadcn primitives backed by Radix.

Specimen
Harness screenshot of hextaui-settings-team-members at 375 pixels wide
Harness screenshot at 375 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-team-members at 768 pixels wide
Harness screenshot at 768 pixels wide. No horizontal overflow recorded.
Harness screenshot of hextaui-settings-team-members at 1440 pixels wide
Harness screenshot at 1440 pixels wide. No horizontal overflow recorded.

Measured

Every value below was written by the harness on the run that produced the frames above. None of it is derived from the prose.

Harness measurements recorded for hextaui-settings-team-members
BuildOK
MountOK
Console errors0
Uncaught page errors0
Horizontal overflowclean at 375, 768, 1440
Axe critical0
Axe serious0
Axe moderate0
Axe minor0
Gzip marginal77.5 KB (142.9 KB build, 65.4 KB baseline)
Bare modeFAIL
Provider requiredNO
Demo usedwritten from the component source API

What the harness recorded

BARE BUILD

✗ Build failed in 1m 21s
error during build:
[vite:load-fallback] Could not load <sandbox>/src/lib/utils (imported by src/cut/blocks/settings/settings-team-members.tsx): ENOENT: no such file or directory, open '<sandbox>/src/lib/utils'

Verdict

A complete settings block with sensible responsive behavior and callback-based integration points. It needs a shadcn-style setup and does not mount in a bare React project, so adopt it when its component stack already matches yours or you are willing to recreate that stack.

Use it if

  • You need a ready-made team settings surface and already use shadcn conventions.
  • Your application owns the invite, role-change, ownership-transfer, and removal APIs.
  • You want responsive member rows with empty, invited, suspended, owner, and current-user states.

Skip it if

  • Your project does not use Tailwind tokens, path aliases, or shadcn-style local primitives.
  • You need built-in confirmation, authorization checks, or recovery handling for destructive member actions.
  • You want a compact dependency footprint for a simple member list.

Install

Installation record for hextaui-settings-team-members
Declared dependencies@radix-ui/react-avatar, @radix-ui/react-slot, @radix-ui/react-dialog, @radix-ui/react-dropdown-menu, @radix-ui/react-label, @radix-ui/react-separator, @radix-ui/react-select
Missing on installnone
Bare installfails once the shadcn-style helpers are removed, so it needs that setup
Providerno provider required in the harness

In a non-shadcn project, add the local class-merging utility, configure the path aliases and Tailwind theme tokens, install Lucide and the required Radix packages, and implement compatible avatar, badge, button, card, dialog, dropdown, field, input group, select, and textarea primitives.

Source and credit

This page is a review, not a copy. The component source lives with its author and this site does not republish it. Read the license before you use anything.

License
MIT
Record published
2026-08-14

Alternatives

Other published entries for the team pattern, ordered by what they measured: mounts first, then clean axe scans, then bare-mode passes, then the smaller bundle.