Skip to content
← All documentation

Dashier documentation

Build an internal operations tool with Dashier

Turn a defined operational workflow into sources, generated admin screens, and governed API access.

An internal tool is useful when it removes repetitive work without hiding who changed important data. Dashier supplies the data-source model, generated CRUD interface, API, roles, imports, and audit history. Workflow-specific rules and external integrations still belong to your application or connected systems.

Choose one workflow

Start with one focused operation: reviewing support escalations, maintaining a product catalog, or tracking event registrations. Write down record types, audiences, and permitted actions. A small workflow is easier to govern than a giant “everything” table.

Model records and actions

Create one source per coherent record type. Give fields clear types, labels, and purposes; add references where records depend on another source; use explicit enum statuses. Dashier validates field values, while rules such as “only an approved request may be fulfilled” need application enforcement.

Configure access before rollout

Assign system or custom roles based on operational duties. Grant only the read/create/update/delete verbs each person needs. API callers have separate authentication and route policies. Test denied requests and invalid values as carefully as successful ones.

Move data safely

Use CSV/JSON preview to map and validate existing rows. Compare samples in the generated table with the source, decide who reviews bulk changes and deletes, and use audit history to examine recorded changes. Do not assume audit history replaces backups or compliance logging without checking your requirements.

Integrate in small steps

Begin with a server-side read, then add the minimum writes. Keep keys out of client bundles, rotate unused keys, and monitor responses. Around Dashier, provide clear empty, loading, validation, and permission-denied states.

A good first release solves one operational task and has an owner for schema, permissions, and data quality. Expand only after that foundation is understood.