Service requests

The service-requests layer is the smaller reference implementation for contributors. It owns its UI, API handlers, policies, translations, validation, types, tests, and Drizzle schema.

Product surface

Authenticated users can create and follow requests in their active organization. Organization administrators and system administrators receive a management view.

The feature contributes:

• user and administrator navigation;
• a route-aware module menu;
• attention and overview dashboard widgets;
• tenant-scoped API routes;
• tables and enums in the service_requests PostgreSQL schema.

Policy

The action vocabulary is create, read, update, delete, list, and manage.

Owners and organization administrators receive all actions. Members can create, read, update, and list requests, but cannot perform management or destructive actions.

Why it is the reference layer

Service requests is small enough to read end to end while exercising every important extension point:

1. Define a typed feature and role policy.
2. Register navigation, a module, menu items, and dashboard widgets.
3. Implement pages and components inside the layer.
4. Protect server handlers through portal core.
5. Scope stored records to the active organization.
6. Own translations and shared types.
7. Test feature registration, policy, locale parity, and schema conventions.

Use it alongside the create-a-layer guide. The service-request user guide documents the current product workflow and its organization-wide visibility. Move to the timesheets feature when you need a larger example.