Data Model and First Feature with Prisma ORM in Makerkit Next.js Prisma

Design a multi-tenant database schema with Prisma ORM and build complete CRUD for feedback boards using Next.js server actions, Zod validation, and React Hook Form.

With your Makerkit environment configured, it's time to build something real. In this module, you'll design the TeamPulse database schema and build your first complete feature: feedback boards with full CRUD operations.

Feedback boards are the foundation of TeamPulse. Each organization creates boards to collect feedback from their team—think of them as categorized containers for feature requests, bug reports, and ideas.

By the end of this module, you'll have a working boards feature that demonstrates the patterns you'll use throughout the rest of the application.

Time: ~2-3 hours

What you'll accomplish:

Design and create database tables with proper multi-tenant relationships
Build a boards list page that fetches data on the server
Implement create, edit, and delete functionality with server actions
Learn the form patterns that Makerkit uses throughout the codebase

Technologies used:

Prisma ORM - Type-safe database toolkit
Zod - Schema validation
next-safe-action - Type-safe server actions
React Hook Form - Form state management

What We're Building

TeamPulse needs two core tables: boards to organize feedback by category, and feedback_items to store individual pieces of feedback. The organizationId foreign key ensures that each board belongs to a specific organization—this is how Makerkit enforces multi-tenancy at the database level.

boards                      feedback_items
├── id                      ├── id
├── organizationId (FK)     ├── boardId (FK)
├── name                    ├── authorId (FK)
├── description             ├── title
├── slug                    ├── description
├── createdAt               ├── type (bug/feature/idea)
├── updatedAt               ├── status
                            ├── voteCount
                            ├── createdAt
                            ├── updatedAt

In this module, we'll focus on boards — the parent entity that contains feedback items. You'll build the feedback items feature in Module 4: Feedback Items.

Step 1: Design the Schema

Let's start by defining the database schema for our boards feature. Add the Board model to your packages/database/src/prisma/schema.prisma file:

packages/database/src/prisma/schema.prisma

model Board {
  id             String       @id
  organizationId String       @map("organization_id")
  name           String
  description    String?
  slug           String
  createdAt      DateTime     @default(now()) @map("created_at")
  updatedAt      DateTime     @updatedAt @map("updated_at")
  organization   Organization @relation(fields: [organizationId], references: [id], onDelete: Cascade)
  @@index([organizationId], name: "boards_organization_id_idx")
  @@index([slug], name: "boards_slug_idx")
  @@map("boards")
}

Don't forget to add the relation to the Organization model:

model Organization {
  // ... existing fields
  boards Board[]
}

Key design decisions:

Multi-tenancy via organizationId: Every board belongs to an organization. This foreign key is the foundation of data isolation—queries always filter by organization to prevent data leakage between tenants.
Cascade deletes: The onDelete: Cascade option ensures that when an organization is deleted, all its boards are automatically removed. This prevents orphaned records in the database.
Performance indexes: Indexes on organizationId and slug speed up the most common queries—listing boards for an organization and looking up boards by their URL slug.
Automatic timestamps: The @updatedAt modifier tells Prisma to automatically set updatedAt to the current time whenever a row is modified.

Step 2: Relations in Prisma

In Prisma, relations are defined directly in the schema file using the @relation attribute. We already added this in Step 1 when we defined the Board model. The relation enables eager loading with include:

// Fetch a board with its organization
const board = await db.board.findUnique({
  where: { id: boardId },
  include: { organization: true },
});
// Access the related organization
console.log(board.organization.name);

Step 3: Run the Migration

Migrations translate your schema changes into SQL that modifies the database. Prisma compares your current schema files against the database state and generates the necessary CREATE TABLE, ALTER TABLE, or other SQL statements.

# Generate migration from schema changes
pnpm --filter @kit/database prisma:generate

This will create a migration file in the migrations directory. Prisma generates the migration file by diffing the current schema with the new schema, and will update the snapshots file to reflect the changes.

You should see the following output:

> prisma migrate dev --config prisma/schema.prisma
Reading config file '/Users/giancarlo/Code/teampulse/packages/database/src/prisma/schema.prisma'
11 tables
accounts 13 columns 1 indexes 1 fks
invitations 8 columns 2 indexes 2 fks
members 5 columns 2 indexes 2 fks
organization_roles 6 columns 2 indexes 1 fks
organizations 6 columns 0 indexes 0 fks
sessions 10 columns 1 indexes 1 fks
subscriptions 12 columns 0 indexes 0 fks
two_factors 4 columns 2 indexes 1 fks
users 13 columns 0 indexes 0 fks
verifications 6 columns 1 indexes 0 fks
boards 7 columns 2 indexes 1 fks
[✓] Your SQL migration file ➜ packages/database/src/prisma/migrations/0001_white_karma/migration.sql 🚀

Note: the actual name of the migration file will be different.

Now, push the migration to the database by running the following command:

pnpm --filter @kit/database prisma:migrate

This will apply the migration to the database.

You should see the following output:

[✓] migrations applied successfully!

Verify it worked:

# Open Prisma Studio to view tables
pnpm --filter @kit/database prisma:studio

You should see the boards table with all columns.

Step 5: Create the Validation Schema

While the database schema defines what columns exist, Zod schemas define what input is valid.

Keeping validation separate from the database gives you precise control over error messages and lets you transform data (like trimming whitespace) before it reaches the database.

apps/web/lib/boards/boards.schema.ts

import * as z from 'zod';
export const createBoardSchema = z.object({
  name: z
    .string()
    .min(3, 'Name must be at least 3 characters')
    .max(100, 'Name must be less than 100 characters')
    .transform((val) => val.trim()),
  description: z
    .string()
    .max(500, 'Description must be less than 500 characters')
    .optional()
    .transform((val) => val?.trim()),
});
// Extend the create schema to include the board ID for updates
export const updateBoardSchema = createBoardSchema.extend({
  id: z.string().min(1, 'Board ID is required'),
});
// Delete only needs the ID
export const deleteBoardSchema = z.object({
  id: z.string().min(1, 'Board ID is required'),
});
export type CreateBoardInput = z.infer<typeof createBoardSchema>;
export type UpdateBoardInput = z.infer<typeof updateBoardSchema>;

Step 6: Create the Server Actions

Server actions handle data mutations in Next.js. They run exclusively on the server, which means they can safely access the database and perform privileged operations.

Makerkit's authenticatedActionClient wraps your actions with authentication checks and schema validation.

apps/web/lib/boards/boards-server-actions.ts

'use server';
import { revalidatePath } from 'next/cache';
import { authenticatedActionClient } from '@kit/action-middleware';
import { getActiveOrganizationId } from '@kit/better-auth/context';
import { db } from '@kit/database';
import { getLogger } from '@kit/shared/logger';
import { generateSlug, generateId } from '@kit/shared/utils';
import {
  createBoardSchema,
  updateBoardSchema,
  deleteBoardSchema,
} from './boards.schema';
export const createBoardAction = authenticatedActionClient
  .inputSchema(createBoardSchema)
  .action(async ({ parsedInput: data, ctx }) => {
    const userId = ctx.user.id;
    const organizationId = await getActiveOrganizationId();
    if (!organizationId) {
      throw new Error('No active organization');
    }
    const logger = (await getLogger()).child({
      name: 'create-board',
      userId,
      organizationId,
      boardName: data.name,
    });
    logger.info('Creating board');
    const board = await db.board.create({
      data: {
        id: generateId(),
        organizationId,
        name: data.name,
        description: data.description ?? null,
        slug: generateSlug(data.name),
      },
    });
    logger.info({ boardId: board.id }, 'Board created successfully');
    revalidatePath('/boards', 'layout');
    return { board };
  });
export const updateBoardAction = authenticatedActionClient
  .inputSchema(updateBoardSchema)
  .action(async ({ parsedInput: data, ctx }) => {
    const userId = ctx.user.id;
    const organizationId = await getActiveOrganizationId();
    if (!organizationId) {
      throw new Error('No active organization');
    }
    const logger = (await getLogger()).child({
      name: 'update-board',
      userId,
      organizationId,
      boardId: data.id,
      boardName: data.name,
    });
    logger.info('Updating board...');
    const board = await db.board.update({
      where: {
        id: data.id,
        organizationId,
      },
      data: {
        name: data.name,
        description: data.description ?? null,
        slug: generateSlug(data.name),
      },
    });
    logger.info('Board updated successfully');
    revalidatePath('/boards', 'layout');
    return { board };
  });
export const deleteBoardAction = authenticatedActionClient
  .inputSchema(deleteBoardSchema)
  .action(async ({ parsedInput: data, ctx }) => {
    const userId = ctx.user.id;
    const organizationId = await getActiveOrganizationId();
    if (!organizationId) {
      throw new Error('No active organization');
    }
    const logger = (await getLogger()).child({
      name: 'delete-board',
      userId,
      organizationId,
      boardId: data.id,
    });
    logger.info('Deleting board...');
    await db.board.delete({
      where: {
        id: data.id,
        organizationId,
      },
    });
    logger.info('Board deleted successfully');
    revalidatePath('/boards', 'layout');
    return { success: true };
  });

Key patterns:

authenticatedActionClient: This wrapper ensures the user is logged in before the action runs. If the user isn't authenticated, the action returns an error without executing your code.
getActiveOrganizationId(): Retrieves the current organization from the user's session. Every database operation includes this ID to enforce multi-tenant data isolation.
revalidatePath('/path', 'layout'): Next.js caches server component output. After a mutation, this function tells Next.js to re-render the page with fresh data. The 'layout' parameter ensures localized routes are also revalidated.
Organization scoping: Every query includes an organizationId check. This prevents users from accessing or modifying boards that belong to other organizations.

Server Actions Documentation

Tip: to learn more about server actions, please refer to the Server Actions Documentation.

Step 7: Create the Data Loader

While server actions handle writes, loaders handle reads. This separation keeps your code organized and makes it clear which functions modify data versus which functions only fetch it.

Loaders are called from server components to fetch the initial page data. These are not an actual Next.js entity, it's just a convention to name these simple functions that fetch data from the database in a Server Component. Whether you want to call them loaders or anything else, it's up to you and has no impact on the functionality.

apps/web/lib/boards/boards-page.loader.ts

import 'server-only';
import { cache } from 'react';
import { getActiveOrganizationId } from '@kit/better-auth/context';
import { db } from '@kit/database';
export const loadBoards = cache(async () => {
  const organizationId = await getActiveOrganizationId();
  if (!organizationId) {
    return [];
  }
  return db.board.findMany({
    where: { organizationId },
    orderBy: { createdAt: 'desc' },
  });
});
export const loadBoard = cache(async (boardId: string) => {
  const organizationId = await getActiveOrganizationId();
  if (!organizationId) {
    return null;
  }
  return db.board.findFirst({
    where: {
      id: boardId,
      organizationId,
    },
  });
});
export type Board = NonNullable<Awaited<ReturnType<typeof loadBoard>>>;
export type Boards = Awaited<ReturnType<typeof loadBoards>>;

Key patterns:

'server-only': This import causes a build error if the file is accidentally imported in a client component. While Next.js should take care of separating server and client code, it's a safeguard against leaking server-side code to the browser and it's recommended to use it.
cache(): React's cache function deduplicates requests during a single render. If multiple components call loadBoards(), the database is only queried once.
Organization filtering: Like server actions, loaders always filter by organizationId to ensure users only see their own organization's data.
Type exports: Exporting Board and Boards types at the bottom lets other files use these types without importing the loader functions directly.

Step 8: Create the Form Component

Forms in Makerkit combine React Hook Form for state management with Zod for validation.

The zodResolver bridges these two libraries, automatically validating input against your schema and displaying field-level error messages.

apps/web/app/[locale]/(internal)/boards/_components/create-board-form.tsx

'use client';
import { zodResolver } from '@hookform/resolvers/zod';
import { createBoardAction } from '@lib/boards/boards-server-actions';
import {
  type CreateBoardInput,
  createBoardSchema,
} from '@lib/boards/boards.schema';
import { useAction } from 'next-safe-action/hooks';
import { useForm } from 'react-hook-form';
import { Button } from '@kit/ui/button';
import {
  Form,
  FormControl,
  FormField,
  FormItem,
  FormLabel,
  FormMessage,
} from '@kit/ui/form';
import { Input } from '@kit/ui/input';
import { toast } from '@kit/ui/sonner';
import { Textarea } from '@kit/ui/textarea';
interface CreateBoardFormProps {
  onSuccess?: () => void;
}
export function CreateBoardForm({ onSuccess }: CreateBoardFormProps) {
  const { executeAsync, status } = useAction(createBoardAction);
  const form = useForm({
    resolver: zodResolver(createBoardSchema),
    defaultValues: {
      name: '',
      description: '',
    },
  });
  const isPending = status === 'executing';
  // Using executeAsync with manual error handling
  const onSubmit = async (data: CreateBoardInput) => {
    const result = await executeAsync(data);
    if (result?.serverError) {
      toast.error(result.serverError);
      return;
    }
    if (result?.validationErrors) {
      toast.error('Please check your input');
      return;
    }
    toast.success('Board created successfully');
    form.reset();
    onSuccess?.();
  };
  return (
    <Form {...form}>
      <form onSubmit={form.handleSubmit(onSubmit)} className="space-y-4">
        <FormField
          name="name"
          render={({ field }) => (
            <FormItem>
              <FormLabel>Board Name</FormLabel>
              <FormControl 
                render={<Input
                  placeholder="Product Feedback"
                  disabled={isPending}
                  data-testid="create-board-name-input"
                  {...field}
                />} 
              />
              <FormMessage />
            </FormItem>
          )}
        />
        <FormField
          name="description"
          render={({ field }) => (
            <FormItem>
              <FormLabel>Description (optional)</FormLabel>
              <FormControl render={<Textarea
                placeholder="Collect feedback from users about our product"
                disabled={isPending}
                data-testid="create-board-description-input"
                {...field}
              />} />
              <FormMessage />
            </FormItem>
          )}
        />
        <Button
          type="submit"
          disabled={isPending}
          data-testid="create-board-submit"
        >
          {isPending ? 'Creating...' : 'Create Board'}
        </Button>
      </form>
    </Form>
  );
}

Key patterns:

'use client': Forms require client-side interactivity, so this directive marks the component as a client component.
zodResolver: Connects your Zod schema to React Hook Form, enabling automatic validation as users type.
useAction: The next-safe-action hook that calls your server action. It provides status to track loading state and executeAsync to run the action.
Error handling: Server actions can return serverError (unexpected errors) or validationErrors (schema validation failures). Handle both to give users clear feedback.
Pending state: Disable form inputs and show loading text while the action is executing to prevent double submissions.

Step 9: Create the Dialog Component

We will use the Dialog component from the @kit/ui/dialog package to create a dialog component that will be used to create a new board. The dialog wraps the form and can be used in any page or component.

Using controlled state (open and onOpenChange) lets you close the dialog programmatically after a successful form submission.

apps/web/app/[locale]/(internal)/boards/_components/create-board-dialog.tsx

'use client';
import { useState } from 'react';
import {
  Dialog,
  DialogContent,
  DialogDescription,
  DialogHeader,
  DialogTitle,
  DialogTrigger,
} from '@kit/ui/dialog';
import { CreateBoardForm } from './create-board-form';
export function CreateBoardDialog({ children }: React.PropsWithChildren) {
  const [open, setOpen] = useState(false);
  return (
    <Dialog open={open} onOpenChange={setOpen}>
      <DialogTrigger render={children as React.ReactElement} />
      <DialogContent>
        <DialogHeader>
          <DialogTitle>Create Feedback Board</DialogTitle>
          <DialogDescription>
            Create a new board to collect feedback from your team.
          </DialogDescription>
        </DialogHeader>
        <CreateBoardForm onSuccess={() => setOpen(false)} />
      </DialogContent>
    </Dialog>
  );
}

Step 10: Create the Boards Page and Layout

Now that we have server actions and a form component, we can create the boards page and layout, so that there's an actual page to display the boards.

Creating the Boards Layout

First things first, we need to create the layout for the boards page. In general, we can copy over the same layout from the Dashboard layout at (internal)/dashboard/layout.tsx.

apps/web/app/[locale]/(internal)/boards/layout.tsx

import { AppSidebar } from '../_components/app-sidebar';
export default function BoardsLayout({
  children,
}: React.PropsWithChildren) {
  return <AppSidebar>{children}</AppSidebar>;
}

This layout wraps the page with a Sidebar and the main navigation, while the children of this Layout will be placed in the main content area.

The AppSidebar component is a wrapper around the sidebar that displays the navigation items. It's a simple component that wraps the children with the SidebarProvider component.

To add the boards navigation item, we need to update the apps/web/app/[locale]/(internal)/_config/navigation.config.tsx file and add the boards route to the routes array.

apps/web/app/[locale]/(internal)/_config/navigation.config.tsx

import { Home, MessageSquare } from 'lucide-react';
import { env } from '@kit/shared/env';
import { NavigationConfigSchema } from '@kit/ui/navigation-schema';
const iconClasses = 'w-4';
export const routes: z.output<typeof NavigationConfigSchema>['routes'] = [
  {
    label: 'common.routes.application',
    children: [
      {
        label: 'common.routes.dashboard',
        path: env('NEXT_PUBLIC_APP_HOME_PATH') ?? '/dashboard',
        Icon: <Home className={iconClasses} />,
      },
      {
        label: 'Boards',
        path: '/boards',
        Icon: <MessageSquare className={iconClasses} />,
        context: 'organization',
      },
    ],
  },
];

In the above I imported the MessageSquare icon from lucide-react to use as the icon for the boards route and added the object to the routes array.

For simplicity, I am using plain English strings instead of i18n keys. You can use i18n keys if you want to translate the label of the boards route by adding the translation to the apps/web/public/locales/en/common.json file:

apps/web/i18n/messages/en/common.json

{
  "routes": {
    "boards": "Boards"
  }
}

Creating the Page to display the boards

This is a React Server Component that fetches data directly during render — no useEffect or client-side fetching needed.

The page calls the loader to get boards, then renders either an empty state or a grid of board cards.

apps/web/app/[locale]/(internal)/boards/page.tsx

import type { Metadata } from 'next';
import { headers } from 'next/headers';
import Link from 'next/link';
import { loadBoards } from '@lib/boards/boards-page.loader';
import { Plus } from 'lucide-react';
import { auth } from '@kit/better-auth';
import { AppBreadcrumbs } from '@kit/ui/app-breadcrumbs';
import { Button } from '@kit/ui/button';
import {
  CardButton,
  CardButtonHeader,
  CardButtonTitle,
} from '@kit/ui/card-button';
import {
  EmptyState,
  EmptyStateButton,
  EmptyStateHeading,
  EmptyStateText,
} from '@kit/ui/empty-state';
import { If } from '@kit/ui/if';
import { PageBody, PageHeader } from '@kit/ui/page';
import { CreateBoardDialog } from './_components/create-board-dialog';
export const metadata: Metadata = {
  title: 'Feedback Boards',
  description: 'Manage your feedback boards',
};
export default async function BoardsPage() {
  const [boards, { success: canCreateBoard }] = await Promise.all([
    loadBoards(),
    auth.api.hasPermission({
      headers: await headers(),
      body: {
        permissions: {
          board: ['create'],
        },
      },
    }),
  ]);
  return (
    <PageBody>
      <PageHeader>
        <div className="flex-1">
          <AppBreadcrumbs />
        </div>
        <If condition={canCreateBoard}>
          <CreateBoardDialog>
            <Button size="sm">
              <Plus className="mr-2 h-4 w-4" />
              Create Board
            </Button>
          </CreateBoardDialog>
        </If>
      </PageHeader>
      {boards.length === 0 ? (
        <EmptyStateSection canCreateBoard={canCreateBoard} />
      ) : (
        <div className="grid gap-4 sm:grid-cols-2 md:grid-cols-3 xl:grid-cols-4">
          {boards.map((board) => (
            <BoardCard key={board.id} board={board} />
          ))}
        </div>
      )}
    </PageBody>
  );
}
function EmptyStateSection({ canCreateBoard }: { canCreateBoard: boolean }) {
  return (
    <EmptyState>
      <EmptyStateHeading>No boards yet</EmptyStateHeading>
      <EmptyStateText>
        Create your first feedback board to start collecting feedback.
      </EmptyStateText>
      <If condition={canCreateBoard}>
        <CreateBoardDialog>
          <EmptyStateButton
            render={
              <Button size="sm">
                <Plus className="mr-2 h-4 w-4" />
                Create Board
              </Button>
            }
          />
        </CreateBoardDialog>
      </If>
    </EmptyState>
  );
}
function BoardCard({
  board,
}: {
  board: Awaited<ReturnType<typeof loadBoards>>[number];
}) {
  return (
    <CardButton
      render={
        <Link className="w-full" href={`/boards/${board.id}`}>
          <CardButtonHeader className="text-left">
            <CardButtonTitle>{board.name}</CardButtonTitle>
            {board.description && (
              <span className="text-muted-foreground max-w-full text-xs">
                {board.description}
              </span>
            )}
          </CardButtonHeader>
        </Link>
      }
    />
  );
}

When the list is empty, we should see the empty state prompting to create a board:

When we click on the "Create Board" button, we should see the create board dialog:

When we fill the form and submit it, we should see the board created and the list updated:

Step 11: Editing and Deleting Boards functionality

Now that create functionality is working, we can add the edit and delete operations.

The edit form reuses the same form structure as create, while delete uses an AlertDialog component to require explicit confirmation before destroying data. These dialogs are preferable to Dialog as they cannot be dismissed by clicking outside of them - which is a better user experience for destructive actions.

Edit Board Form

The edit form is nearly identical to the create form, but it pre-populates fields with existing values and calls updateBoardAction instead of createBoardAction.

apps/web/app/[locale]/(internal)/boards/_components/edit-board-form.tsx

'use client';
import { useAction } from 'next-safe-action/hooks';
import { zodResolver } from '@hookform/resolvers/zod';
import type { Board } from '@lib/boards/boards-page.loader';
import { updateBoardAction } from '@lib/boards/boards-server-actions';
import {
  type UpdateBoardInput,
  updateBoardSchema,
} from '@lib/boards/boards.schema';
import { useForm } from 'react-hook-form';
import { Button } from '@kit/ui/button';
import {
  Form,
  FormControl,
  FormDescription,
  FormField,
  FormItem,
  FormLabel,
  FormMessage,
} from '@kit/ui/form';
import { Input } from '@kit/ui/input';
import { toast } from '@kit/ui/sonner';
import { Switch } from '@kit/ui/switch';
import { Textarea } from '@kit/ui/textarea';
interface EditBoardFormProps {
  board: Board;
  onSuccess?: () => void;
}
export function EditBoardForm({ board, onSuccess }: EditBoardFormProps) {
  const { executeAsync, status } = useAction(updateBoardAction);
  const form = useForm({
    resolver: zodResolver(updateBoardSchema),
    defaultValues: {
      id: board.id,
      name: board.name,
      description: board.description ?? '',
    },
  });
  const isPending = status === 'executing';
  const onSubmit = async (data: UpdateBoardInput) => {
    const result = await executeAsync(data);
    if (result?.serverError) {
      toast.error(`Board update failed`);
      return;
    }
    if (result?.validationErrors) {
      toast.error('Please check your input');
      return;
    }
    toast.success('Board updated successfully');
    onSuccess?.();
  };
  return (
    <Form {...form}>
      <form onSubmit={form.handleSubmit(onSubmit)} className="space-y-4">
        <FormField
          name="name"
          render={({ field }) => (
            <FormItem>
              <FormLabel>Board Name</FormLabel>
              <FormControl
                render={
                  <Input
                    placeholder="Product Feedback"
                    disabled={isPending}
                    data-testid="edit-board-name-input"
                    {...field}
                  />
                }
              />
              <FormMessage />
            </FormItem>
          )}
        />
        <FormField
          name="description"
          render={({ field }) => (
            <FormItem>
              <FormLabel>Description (optional)</FormLabel>
              
              <FormControl
                render={
                  <Textarea
                    placeholder="Collect feedback from users about our product"
                    disabled={isPending}
                    data-testid="edit-board-description-input"
                    {...field}
                  />
                }
              />
              <FormMessage />
            </FormItem>
          )}
        />
        <FormField
          name="isPublic"
          render={({ field }) => (
            <FormItem>
              <div className="space-y-0.5">
                <FormLabel>Public Board</FormLabel>
                <FormDescription>
                  Allow anyone to view and submit feedback
                </FormDescription>
              </div>
              <FormControl
                render={
                  <Switch
                    checked={field.value}
                    onCheckedChange={field.onChange}
                    disabled={isPending}
                  />
                }
              />
            </FormItem>
          )}
        />
        <FormField
          name="allowAnonymous"
          render={({ field }) => (
            <FormItem>
              <div className="space-y-0.5">
                <FormLabel>Allow Anonymous submissions</FormLabel>
                <FormDescription>
                  Allow public board submissions from anonymous users
                </FormDescription>
              </div>
              <FormControl render={
                <Switch
                  checked={field.value}
                  onCheckedChange={field.onChange}
                  disabled={isPending}
                />}
              />
                  
            </FormItem>
          )}
        />
        <Button
          type="submit"
          disabled={isPending}
          data-testid="edit-board-submit"
        >
          {isPending ? 'Saving...' : 'Save Changes'}
        </Button>
      </form>
    </Form>
  );
}

Edit Board Dialog

Like the create dialog, this wraps the form in a modal.

It receives the current board as a prop so the form can display existing values and update the board when the form is submitted.

Once again, I want to emphasize why you should create a separate component for the edit form. Not only we can use it in multiple places, but we can also avoid instantiating the form before the dialog is opened. This lazy-render practice helps improve the performance of the application and the memory footprint - and allows the form state to be cleaned up properly when the dialog is closed, without us needing to worry about it (for example, by manually calling form.reset()).

Let's create the edit board dialog component now:

apps/web/app/[locale]/(internal)/boards/_components/edit-board-dialog.tsx

'use client';
import { useState } from 'react';
import type { Board } from '@lib/boards/boards-page.loader';
import { Pencil } from 'lucide-react';
import { Button } from '@kit/ui/button';
import {
  Dialog,
  DialogContent,
  DialogDescription,
  DialogHeader,
  DialogTitle,
  DialogTrigger,
} from '@kit/ui/dialog';
import { EditBoardForm } from './edit-board-form';
interface EditBoardDialogProps {
  board: Board;
}
export function EditBoardDialog({ board }: EditBoardDialogProps) {
  const [open, setOpen] = useState(false);
  return (
    <Dialog open={open} onOpenChange={setOpen}>
      <DialogTrigger
        render={
          <Button variant="outline" size="sm" data-testid="edit-board-button">
            <Pencil className="mr-2 h-4 w-4" />
            Edit
          </Button>
        }
      />
      <DialogContent>
        <DialogHeader>
          <DialogTitle>Edit Board</DialogTitle>
          <DialogDescription>
            Update your feedback board details.
          </DialogDescription>
        </DialogHeader>
        <EditBoardForm board={board} onSuccess={() => setOpen(false)} />
      </DialogContent>
    </Dialog>
  );
}

Delete Board Dialog

For destructive actions, use AlertDialog instead of Dialog. The AlertDialog pattern requires users to explicitly confirm their intent, reducing the chance of accidental data loss.

After successful deletion, the component redirects to the boards list.

apps/web/app/[locale]/(internal)/boards/_components/delete-board-dialog.tsx

'use client';
import { useState } from 'react';
import { Trash2 } from 'lucide-react';
import { useAction } from 'next-safe-action/hooks';
import {
  AlertDialog,
  AlertDialogAction,
  AlertDialogCancel,
  AlertDialogContent,
  AlertDialogDescription,
  AlertDialogFooter,
  AlertDialogHeader,
  AlertDialogTitle,
  AlertDialogTrigger,
} from '@kit/ui/alert-dialog';
import { Button } from '@kit/ui/button';
import { toast } from '@kit/ui/sonner';
import { deleteBoardAction } from '@lib/boards/boards-server-actions';
interface DeleteBoardDialogProps {
  boardId: string;
  boardName: string;
}
export function DeleteBoardDialog({
  boardId,
  boardName,
}: DeleteBoardDialogProps) {
  const [open, setOpen] = useState(false);
  return (
    <AlertDialog open={open} onOpenChange={setOpen}>
      <AlertDialogTrigger
        render={
          <Button
            variant="destructive"
            size="sm"
            data-testid="delete-board-button"
          >
            <Trash2 className="mr-2 h-4 w-4" />
            Delete
          </Button>
        }
      />
      <AlertDialogContent>
        <AlertDialogHeader>
          <AlertDialogTitle>Delete Board</AlertDialogTitle>
          <AlertDialogDescription>
            Are you sure you want to delete <b>{boardName}</b>? This action
            cannot be undone and will delete all feedback items in this board.
          </AlertDialogDescription>
        </AlertDialogHeader>
        <DeleteBoardForm boardId={boardId} onSuccess={() => setOpen(false)} />
      </AlertDialogContent>
    </AlertDialog>
  );
}
function DeleteBoardForm({
  boardId,
  onSuccess,
}: {
  boardId: string;
  onSuccess: () => void;
}) {
  const { executeAsync, status } = useAction(deleteBoardAction);
  const isPending = status === 'executing';
  const handleDelete = async () => {
    const promise = executeAsync({ id: boardId }).then((result) => {
      if (result?.serverError || result?.validationErrors) {
        throw new Error(result.serverError);
      }
      return result;
    });
    await toast
      .promise(promise, {
        loading: 'Deleting board...',
        success: 'Board deleted successfully',
        error: 'Failed to delete board',
      })
      .unwrap();
    onSuccess();
  };
  return (
    <AlertDialogFooter>
      <AlertDialogCancel disabled={isPending}>Cancel</AlertDialogCancel>
      <AlertDialogAction
        onClick={handleDelete}
        disabled={isPending}
        className="bg-destructive text-destructive-foreground hover:bg-destructive/90"
      >
        {isPending ? 'Deleting...' : 'Delete Board'}
      </AlertDialogAction>
    </AlertDialogFooter>
  );
}

Step 12: Create the Board Detail Page

With the components for edit and delete board created, we can now create the board detail page and put everything together.

Dynamic route segments like [boardId] capture URL parameters. The page fetches the specific board and renders a 404 if it doesn't exist or doesn't belong to the current organization.

The generateMetadata function sets the page title dynamically based on the board name.

apps/web/app/[locale]/(internal)/boards/[boardId]/page.tsx

import type { Metadata } from 'next';
import { notFound } from 'next/navigation';
import { AppBreadcrumbs } from '@kit/ui/app-breadcrumbs';
import { PageBody, PageHeader } from '@kit/ui/page';
import { loadBoard } from '@lib/boards/boards-page.loader';
import { DeleteBoardDialog } from '../_components/delete-board-dialog';
import { EditBoardDialog } from '../_components/edit-board-dialog';
interface BoardPageProps {
  params: Promise<{ boardId: string }>;
}
export async function generateMetadata({
  params,
}: BoardPageProps): Promise<Metadata> {
  const { boardId } = await params;
  const board = await loadBoard(boardId);
  return {
    title: board?.name ?? 'Board Not Found',
  };
}
export default async function BoardPage({ params }: BoardPageProps) {
  const { boardId } = await params;
  const board = await loadBoard(boardId);
  if (!board) {
    notFound();
  }
  return (
    <PageBody>
      <PageHeader>
        <div className="flex-1">
          <AppBreadcrumbs
            values={{
              boards: 'Boards',
              [board.id]: board.name,
            }}
          />
        </div>
        <div className="flex gap-2">
          <EditBoardDialog board={board} />
          <DeleteBoardDialog boardId={board.id} boardName={board.name} />
        </div>
      </PageHeader>
      {/* Feedback items list will go here - see Module 4 */}
    </PageBody>
  );
}

Here's the current state of the board detail page:

When we click on the "Edit" button, we should see the edit board dialog. Please go ahead and test the edit functionality and verify that the board is updated and the list is updated.

You can also test the delete functionality by clicking on the "Delete" button and confirming the deletion.

Checkpoint: Verify It Works

Before moving on, test each piece of functionality to ensure everything works correctly. If any step fails, check the console for errors and review the relevant code:

[ ] boards table exists in database
[ ] /boards page loads without errors
[ ] Can create a new board
[ ] New board appears in list
[ ] Can view board details
[ ] Can edit board name/description
[ ] Can delete board
[ ] Boards are scoped to organization (switch organization in the sidebar to verify)

Before committing your work, it's always a good idea to run the following commands to ensure everything is working correctly:

pnpm typecheck
pnpm lint:fix
pnpm format:fix

You can also run this individual command that runs all of the above checks:

pnpm run healthcheck

Patterns Reference

These are the core patterns you'll use throughout TeamPulse and any Makerkit application. Bookmark this section for quick reference when building new features.

Server Action Pattern

export const myAction = authenticatedActionClient
  .inputSchema(mySchema)
  .action(async ({ parsedInput: data, ctx }) => {
    const organizationId = await getActiveOrganizationId();
    // ... implementation
    revalidatePath('/path', 'layout');
    return { result };
  });

Loader Pattern

export const loadData = cache(async () => {
  const organizationId = await getActiveOrganizationId();
  return db.table.findMany({ where: { organizationId } });
});

Form Pattern

const form = useForm({
  resolver: zodResolver(schema),
  defaultValues: { ... },
});
const { executeAsync, status } = useAction(action);

Module 3 Complete!

You've built a complete feature from database to UI. The patterns you learned here—schema design, server actions, loaders, forms, and dialogs—are the building blocks you'll use for every feature in the application.

You now have:

[x] Database schema for boards with multi-tenant relationships
[x] Server actions for create, update, and delete operations
[x] Data loader with request deduplication
[x] Form with validation and error handling
[x] List page with server-side data fetching
[x] Edit and delete dialogs with confirmation
[x] Navigation integration with i18n support

Next: In Module 4: Feedback Items, you'll build the core feature—feedback submission with voting and status workflow. This module will introduce parent-child relationships in Prisma and more complex form patterns.

Learn More

Dive deeper into the technologies used in this module:

Prisma ORM

Schema Declaration - Defining tables and columns
Relations - Setting up table relationships
Migrations - Database migration workflow
Queries - Select, insert, update, delete

Zod

Basic Usage - Creating schemas
Primitives - String, number, etc.
Objects - Object schemas
Error Handling - Validation errors

next-safe-action

Getting Started - Setup and basics
Action Client - Creating action clients
useAction Hook - Client-side execution

React Hook Form

Getting Started - Basic setup
useForm - Main hook API
Schema Validation - Zod integration

Data Model and First Feature with Prisma ORM in Makerkit Next.js Prisma

Design a multi-tenant database schema with Prisma ORM and build complete CRUD for feedback boards using Next.js server actions, Zod validation, and React Hook Form.

What We're Building

Step 1: Design the Schema

Step 2: Relations in Prisma

Step 3: Run the Migration

Step 5: Create the Validation Schema

Step 6: Create the Server Actions

Server Actions Documentation

Step 7: Create the Data Loader

Step 8: Create the Form Component

Step 9: Create the Dialog Component

Step 10: Create the Boards Page and Layout

Creating the Boards Layout

Adding the Boards Navigation Item

Creating the Page to display the boards

Step 11: Editing and Deleting Boards functionality

Edit Board Form

Edit Board Dialog

Delete Board Dialog

Step 12: Create the Board Detail Page

Checkpoint: Verify It Works

Patterns Reference

Server Action Pattern

Loader Pattern

Form Pattern

Module 3 Complete!

Learn More

Prisma ORM

Zod

next-safe-action

React Hook Form