Skip to content
Features

Admin infrastructure built around your data

Define the operational data your application needs. Dashier provides the generated record interface and REST routes around that model, with roles and API policies you can configure.

AI schema drafts and bulk import plans

Describe a data model in a prompt or supply records. AI Ingest can propose one source or several, prepare an import into an existing writable source, or plan updates matched by a unique field or generated ID. Edit the proposed fields and rows, click Re-validate, then explicitly run a valid plan. Configure your own public HTTPS OpenAI-compatible chat-completions provider and a model with function/tool calling; your prompt and relevant source/list context go to that provider.

Data sources that describe your records

Create a source for each kind of data your team manages. Define typed fields, defaults, enum values, and references; the same field definition informs validation, generated forms, tables, and the REST contract.

Generated admin tables and forms

Dashier builds the record-management surface from a source: list views with search, filters, sorting, and pagination, plus forms to create and edit records. Operators work from the same model used by the API.

Per-source REST APIs

Each data source is available at /api/v1/{source-slug}. Collection routes support list and create operations; append a record ID to read, update, or delete one record. Authentication and endpoint policy determine which callers may use each method.

Roles and endpoint access

Organization members can be assigned system or custom roles; project and source scopes can further define where a member works. API keys have read, write, and admin scopes, while endpoint policies can be Public, Authenticated, or Role-based.

CSV and JSON import/export

Bring in structured files, map columns to source fields, review validation, and export records when needed. Field types and configured choices help surface malformed values before they become application data.

Audit history and scoped keys

Dashier records changes and selected administrative events in audit history. API keys are generated with scopes; the raw key is shown at creation and the application stores its SHA-256 hash. Revoke keys no longer needed.

Email hooks for new records

An Owner, Admin, or Editor can define a record.created hook for a data source, select a custom plain-text template, and send to a fixed recipient. An email field can supply reply-to. Delivery uses a server-side Resend configuration; failed and pending deliveries remain visible for retry.

AI schema drafts and bulk import plans

Describe a data model in a prompt or supply records. AI Ingest can propose one source or several, prepare an import into an existing writable source, or plan updates matched by a unique field or generated ID. Edit the proposed fields and rows, click Re-validate, then explicitly run a valid plan. Configure your own public HTTPS OpenAI-compatible chat-completions provider and a model with function/tool calling; your prompt and relevant source/list context go to that provider.

Why it helps: Use AI for a first draft, not an unattended write. The first preview may require a manual Re-validate click. AI does not create reference fields, train AI models, or provide MCP integration. Bulk writes can partially succeed; inspect results before retrying. Provider compatibility and deployment setup still matter.

Example workflow

Prompt → editable source fields or record plan
Re-validate → review errors → explicitly run
Up to 25 proposed sources; 100 fields and 500 initial rows per source
Existing-source import: up to 2,000 proposed rows
Matched update: up to 500 proposed rows
Prompt: up to 20,000 characters

Examples are explanatory, not screenshots or customer data.

Data sources that describe your records

Create a source for each kind of data your team manages. Define typed fields, defaults, enum values, and references; the same field definition informs validation, generated forms, tables, and the REST contract.

Why it helps: A clear schema reduces drift between what operators enter and what an API consumer expects.

Illustrative data model

Members: name · email · status
Events: title · starts_at · venue
Registrations: member reference · event reference · state

Examples are explanatory, not screenshots or customer data.

Generated admin tables and forms

Dashier builds the record-management surface from a source: list views with search, filters, sorting, and pagination, plus forms to create and edit records. Operators work from the same model used by the API.

Why it helps: Teams can manage operational data without separately coding a CRUD screen for each source.

Example workflow

Define fields → review the table → create or edit a validated record

Examples are explanatory, not screenshots or customer data.

Per-source REST APIs

Each data source is available at /api/v1/{source-slug}. Collection routes support list and create operations; append a record ID to read, update, or delete one record. Authentication and endpoint policy determine which callers may use each method.

Why it helps: Use a documented HTTP interface from a server, web app, or mobile backend instead of coupling every integration to the dashboard UI.

Example workflow

GET  /api/v1/members?page=1&per_page=20
POST /api/v1/members
GET  /api/v1/members/{record-id}
PUT  /api/v1/members/{record-id}
DELETE /api/v1/members/{record-id}

Examples are explanatory, not screenshots or customer data.

Roles and endpoint access

Organization members can be assigned system or custom roles; project and source scopes can further define where a member works. API keys have read, write, and admin scopes, while endpoint policies can be Public, Authenticated, or Role-based.

Why it helps: Separate teammate access from API-client access, and review each boundary independently.

Example workflow

A read-only consumer → read-scoped key or deliberately public GET route
An operator → source grants for the actions their role needs

Examples are explanatory, not screenshots or customer data.

CSV and JSON import/export

Bring in structured files, map columns to source fields, review validation, and export records when needed. Field types and configured choices help surface malformed values before they become application data.

Why it helps: Move existing structured data into the same schema-backed workspace instead of retyping it field by field.

Example workflow

CSV column 'joined_on' → date field
CSV column 'status' → configured enum value

Examples are explanatory, not screenshots or customer data.

Audit history and scoped keys

Dashier records changes and selected administrative events in audit history. API keys are generated with scopes; the raw key is shown at creation and the application stores its SHA-256 hash. Revoke keys no longer needed.

Why it helps: Make key handling and record changes more inspectable; this is not a substitute for independent security review or backups.

Example workflow

Create a project key → keep it server-side → send x-api-key with a request

Examples are explanatory, not screenshots or customer data.

Email hooks for new records

An Owner, Admin, or Editor can define a record.created hook for a data source, select a custom plain-text template, and send to a fixed recipient. An email field can supply reply-to. Delivery uses a server-side Resend configuration; failed and pending deliveries remain visible for retry.

Why it helps: Turn a contact-submission or registration row into a practical notification without making record data control arbitrary email recipients.

Example workflow

New contact row → validated template → fixed inbox
Optional reply-to: the form's email field
Resend: server key + verified sender required

Examples are explanatory, not screenshots or customer data.

Start with a source, not a second application

Dashier is a focused administrative layer. It does not replace your customer-facing product, and framework integrations use its HTTP API rather than a generated SDK. Read the integration guide before placing a key in any client code.

Integrate with your app Follow the AI schema and bulk import guide