Contents
What a workflow is, and what it does not do
A template describes a recurring workflow: name, type and assignment. There are three types: joining, leaving and general. Joining and leaving templates additionally each have an area of their own with full template and task management.
Starting a workflow triggers no action in the system. No accounts are created, no permissions granted and no access revoked. The only exception is the email node in the graphical editor.
That is the honest scope: a guided task list nobody gets past, and no automation quietly doing things in the background.
Building a template
Per template, tasks are created, changed and deleted with a name, description, owner and due date. Selection lists of the members and the departments are available for the assignment.
A template knows no order and no dependencies. All the tasks of a workflow are open at the same time. Anyone needing an order puts it into the due date or the description.
Templates can be assigned per department. That way the workshop gets a different task list from administration, without anyone maintaining two workflows by hand.
- Before a template is deleted, the number of running workflows using it is shown.
- Alongside the list there is a graphical editor in which a workflow is edited as a diagram. The node type picker offers, among others, a task node with an assignment and an email node with its own editor for the subject and text.
Running a workflow
From a template a concrete workflow is created for a person. The owners tick off their tasks, and the progress follows from that.
Running workflows can be paused, resumed and removed entirely. The overview lists running and completed workflows, filterable by type, with figures on the position.
Leaving has one particularity: it also acts on the person's employment period.
Where the tasks appear
Everyone sees the workflow tasks assigned to them in two places: in their own task list and as a tile on the dashboard. Ticking off works in both places, without switching into the workflow.
The details of a task are only loaded when it is expanded, so that the list stays lean.
The introduction for new members
Newly registered members go through a guided introduction of their own. It is separate from the first run management goes through when creating the business, and it is not the same as a joining workflow.
The joining workflow is the business's task list around the new person. The introduction is what the new person sees first themselves.
Follow-up questions
- Does the joining workflow create accounts and access automatically?
- No. The tasks are instructions to people. No accounts are created, no permissions granted and no access revoked. The only exception is the email node in the graphical editor, which sends a message.
- Can a task only be unlocked after another one?
- No. A template knows no order and no dependencies; all the tasks of a workflow are open at the same time. Anyone needing an order represents it through the due date.
- Can different departments get different lists?
- Yes. Templates can be assigned per department, so that different areas get different task lists.
- What happens if we delete a template that is currently running?
- Before removal the number of running workflows using it is shown. The decision stays with you, but you do not make it blind.
- Does the leaving workflow affect the personnel file?
- In one place, yes: leaving affects the employment period. Everything else is tasks that people carry out.
Describes the state of the application on September 2026. What changes in the product is in the product updates.
Published by: AMNAU GmbH
Editorial responsibility: Ugur Aydogan, Product development.
Last reviewed: 14 September 2026