FLOOR 0–1
Capabilities and sources
Asking in your own language, searching documents, calendar and email. Sources connect under a single active connection rule.
Platform
Yaverim Platform is a control tower on your own server: define assistants, run them securely, manage everything from one screen.
Layers
The tower, assistants and capabilities sit on the same screen, in the same product. Each layer works only within its own authority.

FLOOR 0–1
Asking in your own language, searching documents, calendar and email. Sources connect under a single active connection rule.
FLOOR 2–3
The ready-made Yaverim assistant and the assistants you define on screen; each run opens only the tools you allow.
FLOOR 4–6
Assistant definitions, the tool list, knowledge packs, source records, channel and permission rules, the door out, the Approval Center, records, usage limits and model management.
Authority
The limits of a job are set together by the user's permissions, the assistant's rights, what the channel opens up and the type of source. Each layer works only within its own authority.
Approval
The reading path ends with the source shown under the answer; every action that changes data travels one route to the Approval Center. You approve one by one, in a chosen batch or with a second approval; approval times are measured.

Every action that changes data becomes a draft first; there is a single draft route.
The moment you approve, your authority is re-checked. Approval always comes from a person.
Only the work you approved is carried out; even in bulk, every action that changes data counts separately.
The draft, the approval and the work done are recorded with personal data hidden.
Assistants
You define an assistant on screen: name, task description, the tools it may use, the type of source it reads and who owns it. You test the assistant with ready-made questions, and every step it takes stays on record. In jobs that run on their own, an assistant can hand work to another assistant you have allowed, within at most your own authority.

01
Assistants outside your organization ask Yaverim questions only, using a key that belongs to you.
02
The workflow definition, its validation, the side-effect-free pre-check and the executor that runs the steps work together.
Channels
You decide what is open on each channel. Web chat, voice and the external software channel are complete; Telegram, email and jobs that run on their own are limited to questions and drafts; Teams carries notifications and report delivery, and Slack carries report delivery only.
| Channel | Question | Draft | Send | Act |
|---|---|---|---|---|
| Web chat* | on | on | on | on |
| Voice channel | on | off | off | off |
| External software channel | on | off | off | off |
| Telegram channel | on | on | off | off |
| Email channel | on | on | off | off |
| Jobs that run on their own | on | on | off | off |
In web chat too, sending and acting go through a draft you approve on screen.
Features
Everything the product offers, area by area.
Pick an area to open its feature list.
Ask your data
Sources
Documents
Agents
Channels
Voice
Reports and dashboards
Memory and learning
Security
Approval
Model management
Administration
Deployment