Open Arche AI to ask questions about your company's records and indexed documents. Chat requires use_ai_chat, the AI module licence, and enabled company/platform AI settings. Individual features and tools have additional controls.
Questions and tasks
Try a first question
Start with a specific request and add a date range when it matters. For example:
| What you need | Example question |
|---|---|
| Your leave | “What is my current leave balance?” |
| Your pay | “Show my latest payslip and explain the deductions.” |
| Your expenses | “Which of my expense claims are still pending?” |
| A company policy | “What do our uploaded policies say about annual leave? Show the source.” |
| A management summary | “Summarise the latest completed payroll run.” |
| Finding a page | “Where can I review attendance corrections?” |
These are starting points, not a promise of access: your permissions, linked employee profile, company settings and available tools determine what the assistant can retrieve. If the question is ambiguous, specify the employee, pay period or document you mean.
With Tools enabled, try asking for your leave balance, recent payslips, expense claims or employee documents. Self-service tools resolve your linked employee profile. Management tools can look up employees, pay runs, leave requests, recruiting records and reports when your permissions allow them.
The assistant can also retrieve excerpts from indexed company documents for policy and onboarding questions. Document-based answers can display source references; tool lookups show cards with status and expandable input/output. Inspect those sources when an answer matters. An instruction to cite sources or avoid guessing does not guarantee that every generated answer is correct.
Enabled task features include resume screening, interview questions, job-description drafting, performance summaries and payroll anomaly analysis. Availability depends on company configuration. Shift scheduling exists in Arche; see Shift Scheduling for the roster workflow. A feature existing in the app does not mean every operation has an AI tool.
Ask where to find a page when you prefer to carry out a task directly. The assistant's navigation tools can provide application links. The configured chat pipeline uses company documents and registered tools; this guide does not promise public-web research.
Tools and Agentic
| Control | Behaviour |
|---|---|
| Tools | Enabled by default in the web chat. Allows eligible live-data tools. Turning it off removes those tools from the turn. |
| Agentic | Off by default. Requires use_ai_agentic and allows eligible write/action tools in addition to reads. |
There is a self-service exception: streaming chat can offer low- and medium-risk writes on your own records, such as submit_my_leave_request and create_my_expense, with Agentic off. These still require approval and the operation's permission. Non-streaming, non-agentic chat remains read-only.
An administrator can enable or disable tool categories in MCP Tool Settings (/ai/mcp-settings, manage_ai). Platform restrictions and individual tool permissions also affect the available set. Tools are selected for the current feature and question, so the whole catalogue is not necessarily offered in each turn.
Reviewing an action
Confirmation-gated tools show a preview and approval controls. Review the operation and arguments before approving. Denying declines that call. Server-issued approval grants are bound to the user, company, tool and arguments, expire after five minutes, and can be consumed once. Changed arguments need a matching new grant.
The web chat also offers Always allow this session on eligible approval cards. Choosing it approves that tool automatically on subsequent calls during the current chat-page session. Use Approve for a single decision if you want to review each future call separately. Some low-risk tools do not require confirmation at all; Agentic mode is not a promise of a banner for every action.
If an action fails, check the tool result and the corresponding application page before retrying. Approval authorises an attempt; it does not guarantee successful persistence.
Company settings
AI Settings controls enablement, provider/model, feature selection, token budget, PII redaction and custom instructions. Viewing settings uses view_ai; changing them uses manage_ai.
The new-settings entity defaults are AI disabled, OpenAI with gpt-4o-mini, a monthly budget of 1,000,000 tokens, and redaction enabled. Existing companies and provisioning flows may use different values. The chat checks recorded monthly usage before calling the provider; reaching the budget rejects new requests. This is a pre-request check, not a guarantee that an in-flight request cannot exceed the remaining allowance.
Company keys can be configured, with platform-key fallback. Provider choices include OpenAI, Anthropic, Google, Azure OpenAI and a custom OpenAI-compatible endpoint; usable models and credentials depend on the selected provider.
Privacy and audit
Check the answer before acting
Open cited policy sources and inspect the tool results for the relevant dates and records. For a proposed change, check the employee, amount and other details on the approval card. After approving, read the result; a preview or approval alone does not confirm the change succeeded.
If the assistant cannot retrieve something, open the relevant application page or ask your administrator to check your access. Avoid repeatedly submitting a write that may already have succeeded. Never paste passwords or provider keys into chat.
When enabled, redaction masks configured text patterns and known sensitive fields in tool results before the model receives them. Some analytical features deliberately retain pay figures while removing direct identifiers. See AI Privacy & PII Handling for the limits and controls.
AI audit records expose prompt/response information, usage and outcome to users with view_ai. Treat those logs as sensitive: disabling redaction or using an analytical feature changes what may be retained.