Employee portal
Versions, runs and restore: look after an assistant
Every change leaves a version you can restore, every answer is in the runs, a deleted assistant can be restored for 30 days, and sharing with everyone is reviewed first.
Versions
- Each save that changes the name, instructions, sources, actions or schedule leaves a new version, with who saved it and when.
- Open the assistant on the employee portal, expand Versions, and click Restore next to the one to go back to. A restore is a new save; earlier versions stay.
- The last 50 versions of each assistant are kept; older ones are removed.
When someone saved since you opened it
- If someone saved a newer version after you opened the assistant, your save is refused with a message that someone saved a newer version. Close it, open it again, and make your change on the latest.
Test questions
- Open your assistant on the employee portal, expand Test questions, and write up to 10 questions with the answers you expect.
- Click Run tests. The assistant answers each question with its own instructions and sources, as in a conversation, and a model judges whether each answer means what you expected. A run takes a while; you can close the section and the result appears when it is done.
Each question shows Passed, Failed or Not graded (when no clear verdict comes back), with one sentence why and the answer. The result names the version it tested: after you change the assistant it says an earlier version was tested.
Running tests uses the organization’s credits, as any question does. Tests are not conversations: they are not in Runs and do not count toward Not used lately.
When you ask to share with everyone, reviewers see the latest test run on the review list: how many passed, when, and whether it tested an earlier version.
Runs
- Each answer the assistant gives is recorded: when, where (portal, Feishu, WeCom, DingTalk, Slack, Teams, schedule, a change, webhook, group chat), for whom, the outcome (answered, no answer found, refused, failed) and the credits it cost.
- The person who built it expands Runs on the employee portal; owners and admins click Runs next to the assistant in settings.
- You see only the questions you asked yourself and those of runs the assistant started itself; what other people asked is not shown.
- Each turn of a portal conversation with the assistant is recorded too; Duaer Designer answers those, so their outcome and credits are not shown on their own.
- Runs are kept for 90 days.
Delete and restore
- A deleted assistant goes to Recently deleted first: it is not listed, cannot be used and does not run on its own.
- For 30 days, the person who built it clicks Restore under Recently deleted on the employee portal, and owners and admins can restore it in settings. After 30 days it is removed for good, with its versions and runs.
- If the person who built it already has 20 assistants, they delete one before restoring.
Clean up assistants nobody uses
- An owner or admin opens Duaer Settings › Organization › Duaer employee portal › Employee assistants and finds Not used lately.
- Pick a period: no answer in 30, 60 or 90 days. The list shows the assistants that answered nothing in that period and were built before it, each with who built it and the date of its last answer.
- Select the ones to handle, or Select all, then choose Turn off or Delete.
Turning off works as it does for one assistant: the person who built it cannot turn it back on. Delete asks first; deleted assistants go to Recently deleted and can be restored for 30 days. Up to 200 at a time, and each change is recorded in the audit log.
The longest period is 90 days, because runs are kept for 90 days.
Share with everyone in the organization
- The person who built it edits the assistant on the employee portal and clicks Ask to share with everyone.
- An owner or admin sees the request under Shared with everyone in Duaer Settings › Organization › Duaer employee portal › Employee assistants, reads its instructions, and clicks Approve or Reject.
- Once approved, everyone in the organization can use it on the employee portal and in chat tools, each reading only what they may read.
Before approval, and after a rejection, only the person who built it and the colleagues named see it.
Runs it starts itself (schedule, changes, webhook) still go only to the person who built it and the colleagues named, never to everyone.
A later change to the name, instructions, sources or actions sends it back to waiting for review; changing only the schedule does not.
The person who built it can Stop sharing with everyone at any time, and an admin can take back an approval. Requests, approvals, rejections and withdrawals are recorded in the audit log.
Questions
Does restoring an old version lose what is there now?
No. The restore is saved as a new version, and what is there now stays in Versions.
Why don’t I see my colleagues’ questions in the runs?
To keep them private, only your own questions and those of runs the assistant started itself are shown.
Once approved, who sees the assistant’s answers?
Only the person who asked. Each person reads only what they may read, and the answer goes to them alone.
In this section
Employee assistants: build your own assistant on the Duaer employee portal
Employees build an assistant from one sentence: it answers by its own instructions, reads only the sources it is given, runs on a schedule or when something changes, and can be shared with colleagues.
AssistantsLet an assistant run on its own: schedules, changes and webhooks
An assistant can run on a schedule, or when there is new knowledge-base content, a process case changes, or an outside system calls it; results land on each person’s home page and can go to their chat tool.
Security and trustHow Duaer protects your company’s data
Where data is stored, who sees what, encryption, how AI models use your data, how long things are kept, audit and deletion, and how to report a security issue.