Use the AI assistant

The agaro assistant opens as a chat rail inside the dashboard. It can answer with ordinary text and can call authorized tools for the modules your account may access. Those tools reuse the same server actions, validation, workspace scope, and role checks as the rest of the product.

#Open the assistant

Use the assistant launcher in the dashboard chrome. The rail opens without replacing your current page, so you can compare its answer with the source record.

The header provides conversation history and a New conversation action. Collapsing the rail keeps the current conversation mounted so you can return to it without losing the visible transcript.

#Ask a clear question

Include the record, time range, and desired result:

List invoices still unpaid more than 30 days after their due date. Show invoice
number, customer, due date, currency, and outstanding balance. Do not change any
records.

For a change request, state the intended mutation and any limits:

Create a follow up task for the owner of each open opportunity above $25,000.
Due next Friday. Show me the proposed actions before creating anything.

The assistant can only use tools present for the workspace's installed modules and the signed in user's access. If your account cannot read or change a record in the normal product, asking the assistant does not grant that permission.

#Understand a tool turn

During a tool based answer, the rail shows steps as the assistant reads or acts. A write can pause on a confirmation card depending on the selected autonomy mode and the tool's risk class.

Review the tool name, target, and proposed values before accepting. The assistant's natural language summary can be wrong even when a tool result is correct. For financial, legal, payroll, security, or destructive work, open the resulting record and verify it directly.

#Useful requests

Examples include:

• Summarize overdue invoices by customer and currency.
• Find leads without a next activity.
• Draft a task or follow up for selected CRM records.
• Explain recent inventory movement returned by authorized inventory tools.
• Create an expense from exact details you provide.
• Compare workforce or attendance data that your account may read.
• Prepare a marketing draft without sending it.
• Start a supported website project in App Builder.

Tool coverage changes with installed modules and product updates. Ask the assistant to list what it can do in the current context when you are unsure, but treat the actual confirmation card and resulting record as the authority.

#Choose a model

Open the model control in the composer. It shows recommended choices, a searchable model catalog, and the active model. Search by model, provider, or model identifier.

The workspace default is selected under Settings → Developer and AI → Workspace. An admin chooses the default from the platform funded catalog. The composer can choose a model for the current turn or conversation where the UI offers that control.

The platform owns provider credentials for normal workspace use. Workspace users do not paste a personal provider key into the assistant model picker.

#Set reasoning effort

The model panel also contains the per message effort control. Higher effort can use more time and more paid AI usage. Turning Thinking off requests no reasoning mode where the selected provider supports that behavior.

Use a lower setting for short lookups and drafting. Use a higher setting for a complex reconciliation, planning problem, or multistep tool request. A higher setting is not a guarantee of correctness.

#Conversation history

Open history to see your recent conversations, ordered by latest activity. A conversation is scoped to your own user and workspace. Colleagues cannot open it through the ordinary conversation list.

You can return to a conversation, rename it, start a new one, or delete it. Loaded history keeps the most recent portion of very long transcripts. Intermediate live tool plumbing is not replayed as ordinary chat messages.

Deleting a conversation permanently deletes that conversation and its messages. This is different from modules that use Recently deleted.

#Data and accuracy boundaries

The assistant is an AI system and can misunderstand a request or produce incorrect prose. Tool calls are constrained and validated, but generated explanations still require judgment.

Use these practices:

1. Ask for a read only result first when the scope is uncertain.
2. Name the workspace record and date range explicitly.
3. Keep Action on Accept enabled for unfamiliar workflows.
4. Review every confirmation card.
5. Open created or changed records after the turn.
6. Never paste passwords, secret keys, private signing material, or payment card data into chat.
7. Use the secure credential request surface in App Builder when a site requests an approved secret.

#Troubleshooting

#The launcher is present but chat returns module not enabled

The AI Assistant capability is not active for the workspace or your account. Ask an administrator to review the plan, module, and app access.

#The assistant says it cannot change data

The effective mode may be View only, the selected tool may require confirmation, your role may be read only, or the workspace subscription may be inactive.

#A request is rate limited

Wait a minute and retry once. Do not open several tabs to repeat the same turn because assistant requests are limited per user and per workspace.

#A request is blocked by budget

Open Account Settings → AI Usage for personal usage and Settings → Developer and AI → Team AI Budgets for workspace controls if you are an administrator.

#A model is missing

The available catalog is managed by the platform and can change. Choose another listed model or ask an administrator to review the workspace default.