Employee portal
Give employees their own Duaer employee portal
The Duaer employee portal is a separate sign-in address for each organization. Employees see the tasks and decisions workflows push to them and the metrics they follow, and can ask Duaer about them, without opening the workflow editor.
The Duaer employee portal address
Every Duaer organization has its own employee portal, by default at <short-name>.duaer.site. The owner and admins copy the address under Duaer Settings › Organization settings › Duaer employee portal, and can change the short name. The old address then stops working.
The portal and the workflow editor have separate sign-ins: signing in to one does not sign you in to the other.
Your organization's published Webhooks, Chat Triggers and forms use this address too, for example <short-name>.duaer.site/webhook/<path>.
Invite employees to the Duaer employee portal
- Open Duaer Settings › Organization settings.
- Type the email, choose Employee, and click Invite.
- The invite link opens your organization’s portal. They set a password there and from then on sign in to the portal with email and password.
- Forgot the password? On the portal sign-in page, click Forgot password?, enter the email you sign in with, and Duaer emails a link to set a new password. The instance must be able to send email; if it cannot, the page says to ask an admin to reset the password.
- Signed in, click Change password at the top of the portal, enter the current password and the new one twice (8+ characters, a number and a capital letter), plus the verification code under two-step verification. You stay signed in.
Employees are refused by the workflow editor. Owners, admins, and members can sign in to both. To show an employee a metric, add them to the project (for example as viewer), then add them as a viewer in the Duaer metrics catalog.
What employees see in the Duaer employee portal
The Duaer employee portal speaks first: the home page shows today’s date and “N things need your decision today”. Everything on it is pushed by workflows, across every project in the organization.
- The middle is the queue, ordered by what costs more if it waits. Each card shows the rule that was crossed, the facts, a reading, its basis, and the next steps on offer; hovering an option shows what it does. Picking one shows a 5-second countdown on the card with Undo and Run now; only when it ends does that one step run, and then it cannot be undone. Leaving the page during the countdown runs it at once. The card moves to Decided without the page reloading; if it does not go through, the reason shows on the card.
- Cards that workflows or card rules write for you appear while the page is open, without a refresh, marked New; with the tab in the background its title counts your open tasks.
- A plain task without options has Done, with the same 5 seconds to undo. A card put off with Not today moves to the right and can be taken back the same day. When that card names a case, the case path gains a step labeled Not today, from Duaer. Taking the card back leaves the step.
- The left side shows Checked overnight and All normal: what workflows checked and what has no problem. Under that, Cases lists each case this person’s column rule allows, earliest step first. Each step is the activity, when it happened, and the source. A case the rule hides is absent, and the path has no document body. The right side shows Decided: today’s decisions, each marked Done. When the workflow wrote a detail after the step, that line appears under the decision, such as whether a message was sent.
- When nothing needs a decision the page shows “All clear.” with the followed metrics below.
For how to push cards and notes, refer to the Duaer tasks table.
Ask Duaer in the employee portal
Click Ask Duaer at the top, or Ask on a card, to open the dialog on the right. Duaer answers only from that employee’s own cards, notes, and followed metrics, and says which card or note it is citing. When something is not shown to them, Duaer says so.
Duaer never acts on its own. An answer can offer a few options that are already on open cards, and only a click runs one, the same as on the card; an action an admin set up runs once the employee confirms it, unless it is marked Low risk and set to run without confirmation (see the next section). Every question, answer, and model used is kept in the organization’s ask log and billed to the organization’s credits.
Let Ask Duaer run actions for employees
The owner and admins can make a published workflow an action. When an employee asks Ask Duaer for it, Duaer fills in the inputs, and it runs once the employee confirms. Actions for common systems can be added from action packs, where low-risk ones can be set to run without confirmation.
- Build a workflow that starts with Execute Workflow Trigger (When Executed by Another Workflow), set its input data mode to Define using fields below, list the fields the employee gives, and publish it. To know who asked, add a field named requestedBy: Duaer fills in the employee’s email.
- Open Duaer Settings › Organization settings and find Actions in the Duaer employee portal section. Click Add action.
- Choose the workflow, fill in the name and What it does, and say what each input means and whether it is required.
- Under Who can use it, choose Everyone, Roles, or People, and click Save.
When an employee asks “Chase Acme about the late delivery”, Duaer picks the action and lists the inputs it filled in. The employee can change them; Run runs it and Cancel does nothing. A run is waited for up to 60 seconds: on success the answer shows the message the workflow’s last step returned, on failure the reason, and otherwise that it is still running.
Each run is recorded with who ran it, the inputs, and the result, under Runs next to the action and in the audit log. Turning an action off stops employees from using it; when AI rules set Running workflows to Block, no action runs. Employees need no access to the workflow or its credentials.
The same works when you ask the Duaer bot in Feishu, WeCom, DingTalk, Slack, or Microsoft Teams: it answers about your own cards, cases, and followed metrics, such as “Which orders are likely late?”, and when you ask it to do something, Feishu, Slack, and Teams show a card with Run and Cancel while WeCom and DingTalk send a link to confirm on the portal, where the inputs can be changed. An action can be run once, within an hour, only by the person who asked. Questions about company policies and documents are still answered from the knowledge base.
Build your own assistants
Employees can build their own assistants on the Duaer employee portal from one sentence or a template: 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. Each person who uses it gets answers only from what they may read.
- Employee assistants: build, talk, share, and what admins control.
- Assistant templates: Duaer’s ten and your organization’s.
- Schedules and triggers: when it runs and where results go.
- Assistant webhook: let an outside system run it.
- Versions, runs and restore: restore a version, see runs, restore a deleted assistant, share with everyone.
Write documents and spreadsheets
Employees can write documents and spreadsheets on the Duaer employee portal, or ask Duaer to draft or change them. Changes save as you type and earlier versions are kept; you can share them with colleagues, download them as Word or Excel, or save them to your Feishu Docs.
- In the left menu, click Documents, then New document or New spreadsheet.
- Edit a document in place, like an online document: use the toolbar for headings, bold, lists, checklists, quotes, code, links and tables, or type Markdown such as # heading or - list. A spreadsheet works like Excel: formulas, number formats, merged cells, freeze panes, sort, filter, conditional formatting, data validation, find and replace, and several sheets. The first sheet’s first row holds the column names; it can have up to 50 columns and 5,000 rows.
- Changes save when you stop typing; the top bar says Saving… or Saved. Your own edits keep a version at most every 10 minutes, and one is kept before each change by Duaer or a colleague. Click the versions button at the top, open any version and click Restore this version. The last 30 versions are kept.
Ask Duaer: click Ask Duaer and the conversation opens to the left of the document (from the bottom on a phone); say “make the second paragraph shorter” or “add a days-late column”, or select a passage and type the change in the box that appears, or choose Edit with Duaer in the toolbar for Make it shorter, Fix spelling and grammar, Translate into English and more: with text selected it changes that passage, otherwise the whole document. While Duaer works the document cannot be edited; its change then shows in the document and the answer links to it; what it held before stays in Versions, marked as Duaer’s. When Duaer changes a spreadsheet it keeps the values only; the formatting and formulas can be restored from Versions. You can also ask Duaer “list the late orders as a spreadsheet” and it makes a new one. Duaer only changes documents you may edit and only uses what you may read.
Sharing: the person who made it clicks Share, enters a colleague’s email, and chooses View only or Can edit. Colleagues find it under Shared with me; only the person who made it can share or delete it.
Under Export, choose Download Word or Download Excel. Save to Feishu Docs, also under Export, imports it as a Feishu document or sheet that you own and gives a link to open it. This needs Feishu connected in the knowledge base by an admin, the Feishu app granted docs:document:import (or drive:drive), docs:permission.member:transfer and contact:user.id:readonly, and Duaer able to find you by email or your linked Feishu account.
Make Word files from templates
Turn your company’s own contracts, reports and forms into templates. People fill in a few fields and get a Word file laid out exactly like the template; Duaer can fill them from a conversation first, or one file can be made for each data table row.
- An owner or admin marks each place to fill in Word as {{field name}}, for example {{Supplier}} or {{Amount}}. Fields can be in body text, tables, headers and footers, and can be formatted.
- Under Document templates in Settings › Organization settings › Duaer employee portal, click Add template and choose the .docx (at most 5 MB, 50 per organization). Duaer lists the fields it found; you can later Replace file or Remove. These are recorded in the audit log.
- On the employee portal, people go to Documents, click From a template, pick one, fill in each field, and click Download Word or Save to Feishu Docs. The file keeps the template’s layout, fonts and tables; a field left empty stays empty.
In Ask Duaer, say “Draft one from the purchase contract template for East Paper”. Duaer fills the fields it knows from the conversation and answers with a link; open it, check and change the values, then make the file. Duaer never makes the file itself, and the draft is kept 7 days.
In a data table, select rows and click From a template at the bottom. For each field choose a column, or one value for every file; a column of the same name is chosen to begin with. Each row makes one file; more than one download as a .zip, up to 50 rows at a time.
In Process mining, open a case under Cases and click From a template to fill a template with the case’s Case number, Source, Status, Current step, Started, Last step and attributes; fields of the same name are matched, and the rest can be typed in. One Word file downloads.
Files made from templates are not kept in Duaer: they download to your computer or become a new Feishu document of your own.
Bind your own domain to the Duaer employee portal
- Under Custom domain in the Duaer employee portal section, enter a domain such as work.example.com and click Bind. This needs the Starter plan or higher, one domain per organization.
- At your DNS provider, add the two records shown: a CNAME pointing to your organization’s portal address, and a TXT record at _duaer-verify.<domain>.
- Click Verify. Once both records are found the domain shows Active, the portal opens on it, and new employee invites use it.
Change how the Duaer employee portal looks
The owner and admins can make the Duaer employee portal look like their own organization, on every plan.
- Open Duaer Settings › Organization settings and find Appearance in the Duaer employee portal section.
- Click Upload logo and pick a PNG, JPG, or WebP image of at most 256 KB; square works best. It replaces the first-letter seal at once. Click Remove logo to bring the seal back.
- Pick a theme color: Cinnabar, Pine, Indigo, Plum, Ochre, or Ink. It colors the seal, the line on the left of an urgent card, and the line saying what gets worse if it waits.
- Fill in the subtitle (the line under the organization name, up to 40 characters) and the four column titles (up to 20 characters each): Checked overnight, All normal, Decided, and Not today. The preview above follows as you type.
- Click Save. Employees see it the next time they load the Duaer employee portal, including the sign-in page.
Empty fields use the default text, which follows the language the employee picks. Text you write shows as written in both languages. SVG and other formats are not accepted.
Add the Duaer employee portal to your phone's home screen
Employees can install the Duaer employee portal on their phone and open it from the home screen like an app, without the browser address bar. The portal must be opened over https.
- iPhone: open the portal in Safari, tap Share, and choose Add to Home Screen.
- Android: open the portal in Chrome, tap the menu, and choose Install app or Add to Home screen.
- Chrome and Edge on a computer show an install icon at the right of the address bar.
The app is named after the organization. Its icon is the organization's logo when the logo is about square and at least 144 pixels; otherwise it is a white D on the theme color. After you change the logo or theme color, an installed icon can take a while to update.
Without a network it only says it is offline. Cards, metrics, and other data are not kept on the phone.
Give employees tasks from a workflow
Every Duaer project comes with a locked Duaer tasks data table. When a workflow inserts a row with assignee set to the employee’s sign-in email (lowercase) and status set to open, the task shows on their portal home page, overdue in red. With actions set, the row is a decision card.
To wait until the employee is done, set resume_url to {{ $execution.resumeUrl }} and follow the insert with a Wait node: Resume On Webhook Call, HTTP Method POST. When the employee clicks Done, the row becomes done and the workflow continues from the Wait node. Duaer Designer can build this for you. For where to see the results, refer to the Duaer tasks table.
- assignee: the employee’s sign-in email, matched exactly
- title: one line saying what to do
- detail, due, link: context, deadline, and a related http or https link
- status: open when created; done after the employee clicks Done
- resume_url: optional, the continue address of a waiting workflow
- done_at, done_by: filled in by Duaer when the employee clicks Done
Ask for a comment with the decision
A card can carry a comment box: put a short text in the comment_box column of Duaer tasks for an optional box with that label, such as Note; put JSON {"label": "Reason", "required": ["reject"]} and choosing the reject option needs a comment, while other options stay one click. required set to true means every decision needs one; done stands for Done on a plain task.
The employee writes in the box above the options. Choosing an option that needs a comment without one, the card says "Reason is needed for this choice" and does not start counting down. With the comment written, there are the usual 5 seconds to undo, then the comment goes with the choice, also when the page is left. Not today takes no comment.
The comment is kept in the comment column of the row, and a waiting workflow gets comment in what it receives: read it with {{ $json.body.comment }}. On a card sent to Feishu, the comment box is on the card too; an option that needs a comment asks for it there, and the card keeps what was typed.
Ask for fields with the decision
When the next step needs a value it can use, such as a reason picked from a list, an approved amount or a new date, put a JSON list of up to 10 fields in the form column of Duaer tasks: [{"id": "reason", "label": "Reason", "type": "choice", "options": ["Wrong amount", "No invoice"], "required": ["reject"]}, {"id": "amount", "label": "Approved amount", "type": "number"}].
There are four types: text (the default, up to 500 characters), number, date, and choice (one of 1 to 20 options listed in options). required works as for the comment box: true for every decision, option ids for those options, done for Done on a plain task, and left out for an optional field. A field that does not follow these rules is not shown on the card.
The fields are shown above the comment box. Choosing an option that needs a field without filling it in, the card says "Reason is needed for this choice" and does not start counting down; a value of the wrong type is refused. Not today takes no values.
What the employee entered is kept in the form_values column of the row, and a waiting workflow gets values in what it receives: read one with {{ $json.body.values.reason }}. Numbers come as numbers, dates as YYYY-MM-DD, and fields left empty are not there. When the decision goes back to the system a case is in through a webhook, the values go with it; a Feishu approval gets only the comment. On a card sent to Feishu, text, number, date and choice fields are filled on the card: a date picker for a date, a dropdown for a choice. A missing or wrong value (words in a number field) is told in Feishu and the card keeps what was typed; an option that needs a file or a colleague still opens the card in the Duaer employee portal.
Ask for a colleague with the decision
When the next step goes to a person, such as who signs or who reviews, add a field of type person to form: {"id": "signer", "label": "Signer", "type": "person"}. The employee finds a colleague on the card by name, email, title or department; the one picked shows with their name and email, and Change.
A waiting workflow gets the colleague’s email in lower case in values, ready to send them the next card. Only active members of the organization can be picked; someone outside it or a disabled account is refused. On a card sent to Feishu, an option that needs a colleague opens the card in the Duaer employee portal.
Ask for files with the decision
When the next step needs a file from the employee, such as the receipt for an expense, a signed contract or a photo from the site, add a field of type file to form: {"id": "receipt", "label": "Receipt", "type": "file", "required": ["approve"]}. required works as for the other fields.
The employee clicks Add files on the card and picks files; each uploads as soon as it is picked and is listed with its name and size, with Remove. A field takes at most 5 files of up to 20 MB each, and one decision at most 50 MB; programs and scripts (such as .exe, .sh or .js) cannot be added. When a file is refused, the card says why. Files already added are still there after leaving the page and coming back.
A waiting workflow gets files in what it receives: for each field id, the name, type, size and url of each file. A file field is not in values. The url downloads the file without signing in for 7 days; read it in the steps after the decision with an HTTP Request node, for example {{ $json.body.files.receipt[0].url }}, with the response format set to File. A webhook write-back carries the same links in decision.files, and the Duaer Card Trigger gives files with its events.
Signed in on the employee portal, the person who added a file and the members who can open the card’s project can open it. Files no decision used are deleted after a day; deleting a card’s row deletes its files. On a card sent to Feishu, an option that needs a file opens the card in the Duaer employee portal.
Decisions go back to the system a case is in
Once the owner or an admin sets up write-back, some options of a card rule go back to the system the case is in, such as approving or rejecting a Feishu approval as the person who decided. Under Decided, each card says where its decision went: Sending to Feishu approval, or Sent to Feishu approval. When that system does not take it, the card is back in the queue with Not sent to Feishu approval: and the reason, and nothing changed in Duaer.
When a case was handled in its own system (its status is no longer open), is no longer overdue, or has another owner, the next run of the card rule closes its card, and Decided says Handled in its own system.
Questions
Can a Duaer employee open the workflow editor?
No. The Duaer Employee role signs in only to the organization’s employee portal. To let them build, change their role to Member.
Why does an employee not see my task in the Duaer employee portal?
Duaer matches the email exactly. Check that assignee in Duaer tasks is the email they sign in with, in lowercase, and that status is not done.
Does Ask Duaer act for the employee in the Duaer employee portal?
No. The Duaer employee portal dialog is read-only. It can list options already on open cards, and only the employee’s click runs one.
Why is a case missing from Cases in the Duaer employee portal?
Duaer lists a path only for cases that person’s column rule allows. A hidden case stays off the page, and the path does not include a document body.
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.
Get startedRoll out Duaer to your company: the admin checklist
Eight steps take an organization from sign-up to employees asking Duaer every day: people and sign-in, knowledge sources, a check of members and answers, the chat bot, the employee portal, and what to turn on next.
Knowledge sourcesKnowledge sources you can connect to Duaer
Chat tools, drives and documents, CRM and service, mail and meetings, data warehouses: what each source reads and how to connect it, and how the Duaer bot works in each chat tool.
Follow-throughA daily digest of decisions due, from Duaer
To get a daily digest of decisions due, turn on the Duaer daily digest. Each member gets one message a day with what is overdue or due today, what else is open, and related documents. It goes to Feishu, else WeCom, else email.
Knowledge baseDuaer browser sidebar: search from any web page
The Duaer sidebar for Chrome and Edge opens your company knowledge base beside any web page: search, ask, and see what relates to the page.