Customer panel
The panel is at app.datafala.com.br/login. This is where your tenant's administrator prepares everything the API uses to generate SQL. The schema and context go in only through the panel; the /v1 API does not change configuration.
| Screen | What it is for |
|---|---|
| Home | Summary of the setup, questions from the last 30 days and end-user usage (active in the month, band and previous months). |
| Schema | Dialect (PostgreSQL, MySQL or Firebird 2.5+) and DDL. Shows the recognized tables, columns and foreign keys; lets you describe and hide each one. For Firebird, paste the output of isql -x in SQL dialect 3. |
| Context | Business rules and glossary in free text. |
| Examples | Question → SQL pairs (up to 200), validated by the SQL Guard when saved. |
| Playground | Test questions with the same pipeline as /v1/ask, seeing the rejection reasons without masking. |
| History | Recent questions with status, rejection reason, the user's rating and comment, the prompt sent to the LLM and the "Promote to example" button. |
| Evaluation | Up to 50 question → expected SQL cases, run in batch to measure quality after changing the schema, the context or the model. |
| Credentials | Create, list and revoke API keys. |
| Settings | Your LLM provider, model and key (with a test before saving), the customer name, the default language and the panel theme. |
How to improve the answers
- Describe what is not obvious. A column
stwith valuesA,C,Pneeds a description ("status: A = active, C = cancelled, P = pending"). - Hide what must not be used. Personal or internal data columns do not go into the prompt and are rejected by the Guard.
- Write rules in the context. "Revenue is the sum of
valor_totalfor sales withstatus <> 'C'." Do not put secrets there. - Add examples for the most common questions and for the ones that went wrong. A 👍 feedback in the History becomes an example with one click.
- Build an evaluation with the questions that matter and run it after every change.
Updating the schema
Pasting a new DDL creates a new schema version. Descriptions and hidden markings are copied to the tables and columns with the same name. Answers already stored in the history are not revalidated against the new schema.