Once a source exists, its field definition drives the generated record form and table. That keeps the operator interface and API validation aligned, but it also means a schema edit should be reviewed as a change to both the administrative workflow and the consuming application.
Create a record
Open a source in the project, choose the create action, and complete the generated form. Values are checked against configured types: enum values must be allowed, dates must parse as dates, and references identify records in the target source. Server-owned values—the identifier and any auto-generated timestamp—appear read-only and cannot be edited by hand. Review the new row before sharing the endpoint with another system.
Find and update records
The source table supports searching, sorting, filtering, and pagination. Open a row to edit it. If an update changes a field an application consumes, check that application’s assumptions first—for example, an enum value may be rendered as a label or mapped to logic outside Dashier.
API clients retrieve a record with GET /api/v1/{slug}/{id} and update it with PUT /api/v1/{slug}/{id}. Updates are validated and merged with the existing record; the request still needs authentication and the relevant endpoint policy. See the API guide.
Delete carefully
Deletion is available in the interface and through DELETE /api/v1/{slug}/{id}. Treat it as destructive: verify the source and row, check downstream references or exports, and reserve delete access for roles that need it. Dashier does not automatically clean up dependencies in your application or other systems.
Keep an operational trail
Dashier includes audit history for changes. Use it to inspect important maintenance and make role assignments accountable; it is not a substitute for backups or a compliance system unless it meets your requirements. Preview imports and validation results before applying them. See CSV import and Permissions.
