Getting Started

This page takes you from an empty workspace to the first answer from your own data. Three steps, in order: sign in, connect a source, run a query.

1. Sign in

Open your Datamind address and sign in with the account your administrator created. There is no self-service signup: accounts are created by an administrator, and the role on the account decides what you can see and change.

Role	What it can do
Viewer	Read pages and dashboards, run read-only queries
Editor	Build queries, save them, schedule refreshes
Administrator	Manage users, connectors and workspaces

Note

If you can sign in but a workspace is empty, the account is fine and the workspace has no data connected yet. That is step 2.

2. Connect a data source

A connector is a named set of credentials plus the schedule that reads from it. Add one from Connectors -> New connector, choose the type, and fill in the connection details.

json

{
  "name": "production-postgres",
  "type": "postgres",
  "host": "db.internal.example.com",
  "database": "app",
  "schema": "public"
}

Nothing is read until the first sync runs, and the first sync always runs in full. Every later sync reads only what changed.

3. Run your first query

The query editor runs against the lake, which is where synced tables live. Write SQL, run it, and the result comes back as a table you can chart or export.

sql

select
    status,
    count() as orders,
    sum(total_amount) as revenue
from lake.orders
where created_at >= today() - 7
group by status
order by revenue desc

:::card Before you continue

The connector's first sync has finished. A table that exists but is empty is usually a sync that is still running.
You can see the table in the left-hand tree. If it is missing, the connection is not in the workspace you are looking at.
Your account can read the underlying source. Access is checked at the source, not at Datamind. :::

Next steps

Connect your data source - the connector form, field by field.
The lake - how synced tables are organised and why history is kept.
Running queries - saving, sharing and scheduling queries.