Guided journeys

Choose where the data comes from (customers, receivables, contracts or requests), tick the columns you are interested in and give it a name. The dataset appears immediately as a source in the dashboard builder, alongside the standard sources.

Create your own data source for dashboards, without writing a query: choose a source (customers, receivables, contracts, requests), tick the fields and give it a name. Scoping by company is automatic — another account's data has no way to get in. — this is the role of the "My datasets" screen within the platform.

In New, choose the source (customers, bills, orders…), tick the fields you need and give it a name. Tenka builds the query restricted to your company — you write no SQL — and the dataset shows up right away among the panel builder’s sources.

Each dataset created gets a KEY (the code shown in the list, in a monospace font): that is how dashboards and Explore data reference the source — the name is a label for people, the key is the technical link. In the fields, the suffix (Σ) marks METRICS: numeric columns that accept sum, average and count in dashboards. A field without Σ is a dimension — it is used to group and filter, not to sum.

The screen became the standard list: search, filters, saved views, columns, export and trash with Undo. Click the record (or New) to open the form, with the detail tabs when there are any.

Every dataset created here sees only the data of the company in use. This is not an option someone ticks: the query is generated with the scope built in, from a catalog the user does not edit. It is by design that another account's data has no way to get in.

The turn-off button in the list DEACTIVATES the dataset after a confirmation: it goes out of use for new dashboards, but it is not deleted. The reason is to protect what already exists: an old dashboard that points to that dataset's key keeps working instead of breaking. If you created a dataset by mistake, deactivate it and create another with the right name — there is no way to delete it permanently from the screen, and that is intentional.

In the record's activity panel, each note has "Turn into request". The click creates a ticket with the note's text, who wrote it and the link to this record — nothing is retyped. Use it when the note is a request for action ("someone needs to review this"); the note stays where it was. The button only appears once the record has been saved; a read-only session (demo) doesn't create one.

Deleting a dataset deactivates it: it leaves the sources for new panels, but components already using it keep answering, because they store its key. To offer it again, open the form and switch "Active" on.

Once saved, only the name and "Active" change: the source-and-fields combination is the contract with the panels. Need another combination? Create a new dataset.

There is a layer of validated queries (read-only SQL, reviewed before running) for those who know how to write the query and need joins or calculations that the form does not cover. This screen is the short path; the other is the full path — the two coexist on purpose.

"Can I build a dashboard with MY fields, my way?" — when that question comes up, this is the screen that answers it.