Settings / People & Roles

Where an admin decides who is in the workspace and what they can do: members and invites, seats, what each role may do, a regular access review, and handing the workspace to someone else.

Get pro lifetime to installPro screen · 4 examples · built from 12 Liro components
Open full screen

When to use

  • The team page of a B2B product
  • Offboarding people who own automations or keys
  • Regular access reviews for compliance

When not to use

The decision inside it

Removing someone hands over what they own first

Before a person is removed the screen lists their agents, API keys, documents and scheduled runs, and each one must go to a teammate or be archived. Nothing is left without an owner and no running agent stops silently.

Installation

Settings / People & Roles is a Pro screen, included with pro lifetime. It is two files on top of the Liro components it is made of.

  1. Add the components it uses:
    npx shadcn@latest add @liro/access-review @liro/alert @liro/state @liro/badge @liro/button @liro/dialog @liro/members-table @liro/permissions-matrix @liro/seat-usage @liro/select @liro/tabs @liro/transfer-ownership
  2. Copy screens/people-roles-screen.tsx and screens/data/people-roles-screen.ts from the Code tab above into your project, at the same paths.
  3. It also imports @/lib, @/demos/liro-mark, @/demos/portraits, @/demos/screen-kit and @/demos/settings-shell: Liro’s shared helpers and the demo’s sample images. Point them at your own.

Usage

app/page.tsx
import { PeopleRolesScreen } from "@/screens/people-roles-screen";

export default function Page() {
  /* A screen fills the box it is given: give it the window. */
  return (
    <main className="h-dvh">
      <PeopleRolesScreen className="h-full" />
    </main>
  );
}

Built from

Every Liro component this screen imports. Each has its own page, props and install command.

API reference

Read from PeopleRolesScreenProps when the site is built. It also takes every attribute a div does, such as className.

PeopleRolesScreen

TypeNotes
statePeopleRolesState No–
onRemove(memberId: string, handover: Record<string, string>) => void | Promise<void> NoRemove a person after their things are handed over: item id to new owner id, or "archive".
loadingboolean NoThe data is on its way: the frame stays and the content is drawn as gray shapes in the shape of the real page.
emptyboolean NoThere is nothing yet: each screen says what goes here and offers the one action that fills it.
onNavigate(label: string) => void NoCalled with the label of a sidebar or settings item when someone opens it ("Inbox", "Model policy"). Without it, a toast says where it would go.
workspaceScreenWorkspace NoThe workspace at the top of the sidebar.
userScreenUser NoThe signed-in person, at the bottom of the sidebar.
layoutScreenLayout No"inset": the page on a card beside a gray sidebar. "flat": the page edge to edge. Default "inset".
classNamestring No–

Accessibility

  • The hand-over is a labelled list, and Remove stays disabled until it's complete, with the reason shown
  • Role changes are confirmed in words
  • Tables follow the table pattern with headers
  • Movement follows the reduced-motion setting

Responsive behavior

  • Fills the box it is given: mount it at the window's height
  • Tables scroll sideways inside their card on narrow widths
  • Light and dark come from the Liro theme: it follows the dark class on <html>, like every component.

More screens

Liro · 270 components · 17 screens · 4 templates