Getting started with Dashier

Dashier gives a team one place to define operational data, manage it in generated tables and forms, and connect an application through REST endpoints. The product hierarchy is Organization → Projects → Data Sources → Records. Keep it in mind as you set up: an organization contains projects, a project groups related sources, and each source describes a collection of records.

1. Create your account

Open Dashier and continue with Google. Google OAuth is the sign-in method currently implemented; email-and-password registration is not available. After sign-in, Dashier sends you to the organization area.

2. Create an organization

Create an organization for the team or product that will own the data. Choose a name that people in the team will recognize. Organization membership is the outer access boundary; organization members can then be assigned project and, where configured, data-source access.

3. Create a project

Create a project inside the organization. A project is a practical container for sources that belong to the same application or workflow. For example, a club operations project could hold Members, Events, and Registrations. Keep unrelated apps in separate projects so keys, policies, and access can be managed deliberately.

4. Define a data source

Create a source, give it a URL-safe slug, and add fields. A source called “Members” might use name, email, and status fields. Choose appropriate types and set defaults or enum choices where useful. References can connect one source to another. The field definition is used to build the forms, table behavior, validation, and API contract.

5. Add or import records

Add a record with the generated form, or start with CSV/JSON import. Review the mapping and validation before applying a file. Use representative test data first, then confirm access and endpoint policies before connecting production application flows.

6. Connect your app

Each source has a REST endpoint at /api/v1/{source-slug}. Create a project API key in Dashier and keep it on a server, never in browser code or a mobile binary. Requests can be scoped by key permissions and endpoint policy. See API generation and integration guides for examples.

Before using real customer data

Set roles deliberately, test the access paths you intend to expose, and avoid placing secrets or sensitive data in public-read sources. Dashier’s public site does not publish an SLA or a complete legal privacy/terms package yet. Review the security information and contact support@dashier.app if your deployment or data-handling requirements need confirmation.