Skip to content
← All documentation

Dashier documentation

Getting started with Dashier

Create an account, organization, project, and your first data source.

Dashier gives a team a place to define operational data, manage it in generated tables and forms, and connect an application through REST endpoints. The hierarchy is Organization → Projects → Data Sources → Records: an organization contains projects, each project groups related sources, and a source describes one 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 signing in, you land in the organization area.

2. Create an organization

Create an organization for the team or product that owns the data. Organization membership is the outer access boundary; members can then receive project and, where configured, data-source access. Use a name your team will recognize later when several environments or products exist.

3. Create a project

A project keeps sources for one application or operational area together. A club operations project, for example, might contain Members, Events, and Registrations. Keeping unrelated applications in separate projects makes keys, policies, and access easier to review.

4. Define a data source

Create a source, give it a URL-safe slug, and add fields. A Members source might use name, email, and status fields. Choose types, defaults, and enum choices deliberately; references connect records across sources. The schema drives the generated table, form, validation, and API contract.

5. Add or import records

Add a record with the generated form, or begin with CSV/JSON import. Preview the mapping and validation before applying a file. Use representative test data first, then verify 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 putting 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.