Uktupus Docs
Core

Sona assistant

Ask Sona about your data and about how Uktupus works. Sona can propose creates, updates, and document actions, which you confirm with one click.

Open Sona from the sidebar. Access is a right you grant per role.

What Sona can do

Answer questions about your company data

Sona calls read-only tools scoped to the active company and your permissions: open invoices for a customer, stock of a product per warehouse, who is on leave this week, overdue purchase orders, trial balance for a period… If your role cannot read something, Sona says so instead of guessing.

Explain how Uktupus works

Sona knows the sitemap and process rules in these docs (where a screen is, what posting does, payments vs bank registers, Team vs Employees, which pack shows which tax screen).

Show me (visual tour)

Ask where to create or find something, or say show me. Sona starts a cursor tour on the real UI (sidebar → screen → New when the page has one) instead of a long written guide. Tours cover the sidebar screens from navigation.

Change records — propose, then confirm

Sona never writes directly. When you ask it to create, update, or run a document action:

  1. Sona looks up the business object (fields, labels, and the actions allowed from its status) and proposes the change. The backend checks your permissions, the company plan, and hidden fields, builds a preview, and stores a short-lived proposal (15 minutes, bound to you, the company, and the record version). Nothing is written yet.
  2. A confirmation card appears in the chat showing the preview.
  3. You press Confirm. That button is the only way the change is saved. Sona cannot confirm it. Confirm checks permission, the record's current status, hidden fields, and closed periods again. If the record changed after the proposal, confirm is refused and you ask again. Creates and updates use the same rules as the form. Status, stock, and money actions use the same document action as the screen, including approvals, segregation of duties, and closed periods. Cancel discards the proposal on the server.

Any business object in Uktupus is available this way. A new one does not need a separate Sona tool. Reports that are not a single record (aging, revenue leaderboards, who is on leave) stay as their own answers.

Rules: you need the same right you would need on the screen; proposals expire after 15 minutes; a proposal can be confirmed once, and only by the person who proposed it in that company. Reads follow the same field and company visibility as the matching screen, including compensation. Aging answers match the finance aging screen.

Good prompts

  • "How much does Alkaloid owe us and which invoices are overdue?"
  • "Stock of SKU 10023 in all warehouses."
  • "Create a quotation for Makpetrol with 10 × Filter A at 120 MKD."
  • "Why doesn't my bank register line clear the customer's invoice in the ledger?"
  • "Who approves purchase orders above 50,000?"

Limits

Sona cannot delete records, and it cannot change status, stock, or money except by proposing a document action. Actions that are not document services stay on the screen. It cannot see other companies, modules your plan does not include, or fields your role cannot view. It does not invent numbers — when a tool is forbidden it reports the missing permission.