Skip to content
Dashier

Dashier use cases

Put the record-management work on a clear footing

Dashier fits projects where a team needs to model structured records, manage them in generated admin screens, and connect an application through REST. Here are a few concrete ways to use that layer—and where your own application still does the work.

Start with the docs Explore features

Examples that start with real records

Each example uses the same building blocks: sources, typed fields, generated tables and forms, REST endpoints, and access controls. The difference is the records your project needs to manage.

01 · Contact intake

A website contact form

Contact submissions · name, email, subject, message

  1. 1Your site renders the form and posts it to a route on your server.
  2. 2That route validates the fields and creates a record through the Dashier REST API using a server-only key.
  3. 3Optionally, a record.created email hook sends a saved plain-text template to a fixed team inbox.

Dashier provides

A typed submissions source, generated table and form for staff, a REST endpoint, and an optional fixed-recipient email hook. The hook uses a server-side Resend configuration.

Your application still owns

You build the visitor-facing form and server route, and decide how to handle abuse, confirmation, replies, and retention. Never expose a private Dashier key in browser code.

See the contact-form walkthrough

02 · Membership records

A club or community project

Members · Events · Registrations, with references between records

  1. 1Import an existing member list from CSV and review the field mapping and validation.
  2. 2Let staff search and update member, event, and registration records in generated tables and forms.
  3. 3Connect a club site to the records it needs through server-side REST requests.

Dashier provides

Related data sources, generated record-management screens, CSV/JSON import and export, role-based access, audit history, and per-source REST routes.

Your application still owns

The club's app still handles public sign-up, eligibility, attendance rules, dues, capacity, and payment processing. References organize records; they do not implement those business rules.

Read the membership model guide

03 · Catalog operations

A product catalog for an application

Products · sku, name, price, stock, active

  1. 1Define product fields and, if useful, a reference to a Categories source.
  2. 2Give staff a generated table and form to maintain catalog records.
  3. 3Have your application server read the fields it needs from the product REST endpoint.

Dashier provides

A shared field definition for the generated admin interface and API, plus validation, permissions, and record history for supported changes.

Your application still owns

Your application owns checkout, payment, tax, pricing rules, stock reservation, and any consistency rules that span products and orders.

Learn how to model data sources

04 · Staff operations

A small support-request queue

Requests · requester email, subject, status, assignee, notes

  1. 1Store each request as a record in a source with fields that match how the team works.
  2. 2Use generated search, filters, forms, and roles to find and update requests.
  3. 3If useful, configure a record.created hook to send a selected plain-text notice to a fixed inbox.

Dashier provides

A structured queue for ordinary record work, access controls for teammates, audit history, REST access, and the narrowly scoped new-record email hook.

Your application still owns

Automatic assignment, SLA timers, escalation, customer replies, and multi-step approvals belong in your application or a dedicated workflow service.

Read the internal-operations guide

Common structure

Every project follows the same data path

Organization → Project → Data source → Records

Start with the records and the people who need to manage them. Define fields and references, check the generated forms and API with sample data, then configure permissions before connecting production traffic. Keep domain rules and customer-facing interactions in the application that owns them.

Getting started REST API reference Roles and permissions

See whether Dashier fits your project

Compare the concrete requirements against the current features and integration guide. Pricing remains on its own page.

Integration guide Pricing