User guide
Quick Start Guide
Case notes
Table component
FAQ
Search
Dashboard
Deleted Documents and Access Log
Solving a task
AI Assistant
Manuals
Substitution and Vacation
Suspending, resuming, archiving and deleting a case
Case variables, history and graph
Basic Terms
Uploading Documents, Folders and Revisions
News
Favorites
Navigating the interface
Dashboard widgets
Case Detail
News/Announcements in Team assistant
Case list
Logging In and Out
Account Settings
Task List
Mobile app settings
Reports and Charts
Searching and Listing Documents
Handing Over, Taking Over and Tasks to Pull
Bulk Tasks
Printing a Case
Creating and Editing an Overview
What Is TAS
Form Fields
Tablet Interface and NFC
Overviews
Creating a New Case
Case Events
Case Permissions
Subscribing to an overview by email
Administrator Guide
Platform guide
Administration
Crons
Authentication and Synchronization
SMTP OAuth authentication
LDAP, SAML, Entra ID and NFC: Settings
Configuring authentication modules
Authentication
Vault
DMS attributes
Service Operations
Mobile App Setup for Your Environment
Scheme
XML Process Import
HR agenda and agenda handover
Logs
Archiving
Scripts
Sequences
System Status
News Management
Migrations
Configuration
Plugins
Email Queue
Service Console
AI monitoring
Shared Files
Settings
CSP Headers
CSV Files
Scheduled Tasks
Processing Queues
Maintenance
Administration Menu
Licenses
Dynamic Tables
Usage Statistics
Access Token Settings & Session Expiration
Visual Identity
Template
Prints
Tasks
Task calculations
Automatic task completion and cancellation
Email Task and Notifications
Task types
Smart Event task
Instructions, Sections and Testing a Task
General task settings and solver
Multi-instance
Planning: start, branching and due date
Dynamic conditions: builder
Variable assignment and sections
Variables
Class diagram, object state import and alias candidates
Document list
Text and Multiline text
Checkbox
Number
Variables: overview and common settings
Lists (texts, numbers, dates)
Dynamic Rows
Date
Dynamic list
Sequence
Dynamic Table
Shredding Process
Template graph
Template Tab
Template List
Importing, Exporting and Copying a Template
Template Headers
Case statuses
Roles
Connecting to a different database
Diagnosing services
Hyper-V: Isolated NAT Network with Port Forwarding
Users
Translations
NFC Integration
Events and Rules
AXIOS API
Plans
Axios with Vault
Users
Axios with SSL Certificate
User Detail
Calculations & Functions
Form condition
Other dynamic conditions
Optimization of API calls on dynamic conditions
Filtering in a dynamic sheet using dynamic conditions
Dynamic Conditions: Script
Dynamic Rows: Script
Calculations
Dynamic Tables
Printing and File Generation
Documents in Calculations — Complete Guide
Printing and File Generation in Calculations
DOCX document creation
Other Calculations
How and when calculations run
Calculations API reference: the lib library
Calculations API reference: variables and case
Global Scripts and React Scripts
Integrations
MS Graph
MS Graph - cron configuration
MS Graph v2 (from v5.7.102)
MS Graph - preparing the mailbox
MS Graph (email)
ISDOC.PDF
DocuSign
TAS call module - TAS 2 TAS (process creation via API)
DB View
DocuSign and electronic signatures
ERP and other integrations
Smart Events for Integrations
TAS Forms
TAS Forms
Activating the module on the environment
TAS Forms - secret creation guide for Docker Swarm
Advanced Features & Tips
Filtering in a dynamic sheet using a URL parameter (static)
Optimizing Overviews with a Large Number of Cases
API Documentation
Product
Technical Changelog
Business Changelog
Version Upgrade Guide
Upgrade to v5.19
Upgrade to TAS 5.19 - Key Changes and Removed Features
Upgrading TAS 5.17 to 5.19 – Technical Part (DevOps)
Upgrate to v5.17
Upgrade to TAS 5.17 - Key Changes and Removed Features
Asset Migration from FE to Backend (5.17 Upgrade) — DevOps
Upgrading to v5.7
Lodash upgrade v4.17.x (>v5.5)
Main changes and deprecated features (v5.3 > v5.7)
Highlighting variables in Read-only status (>v5.7.58)
Upgrading to 5.3
Dynamic conditions migration
PDF printing adjustment
Editing Task Description vs Task Instructions
Transpiling forEach to a for loop
Rendering HTML on Caseoverview
Differences between TAS4 and TAS5 - a complete overview
Best Practices for Upgrading from v4 to v5
Using validation functions
Technical details
Server prerequisites
Security and Data Protection
Security
TAS Operations Runbook
Technological architecture
News / Important information
Microsoft Disabling Basic Auth for SMTP
End of EWS support and transition to Microsoft Graph
Adjustment in EWS after MS Exchange update (29.04.2025)
Security notices
Getting Started
- All Categories /
- Administrator Guide
- Platform guide
- Template
- Tasks /
- Email Task and Notifications
Email Task and Notifications
An Email notification task sends an email and then completes itself straight away. You set the recipients, subject and content on the Email tab in the task editor. The subject and the content can have a version for each language and can contain case variable values. An email notification has no solver, and mandatory variables are not checked for it.

| No. | Element | Purpose |
|---|---|---|
| 1 | Send test | Sends a test email to the address you enter, see below. The button is only on the Email tab. |
| 2 | Recipient | Who the email is sent to. The default is Case owner. |
| 3 | Additional recipient field | Depends on the recipient type: task, address, organizational unit, variable or role. Mandatory. |
| 4 | Reply-to recipient | Who replies go to. Default means no separate reply-to address. |
| 5 | Copy recipient | Copy of the email. No means no copy. |
| 6 | Blind copy recipient | Blind copy. No means no blind copy. |
| 7 | Subject | Email subject for the first system language. |
| 8 | Add variable | Inserts a variable into the subject in the form {nazevPromenne}. |
| 9 | Other language variants | Opens the subject for other languages. The AI translation button next to it translates the subject if AI is enabled. |
| 10 | Add custom headers (X-headers) | Turns on custom email headers. |
| 11 | Header | Header name and value. The value can contain variables. Delete a row with the bin icon. |
| 12 | Add header | Adds another header row. |
| 13 | Default content | Email text in the rich text editor. A new task comes with a pre-filled template containing a logo and a link to the case. Below the editor, the Other language variants link opens the content for other languages. |
| 14 | Insert variable | The {v} editor button opens a dialog for inserting a template variable or a system value. |
| 15 | Insert snippet | The {s} editor button inserts a ready-made block, such as an overview or the history. |
Recipient types

All four recipient rows offer the same types. Reply-to recipient also has Default, and copy and blind copy also have No.
| Type | Additional field | Who the email is sent to |
|---|---|---|
| Case owner | none | The case owner. |
| Task supervisor | none | The supervisor of this email task. If none is set, the case owner. |
| Task solver | template task selection | The user who last solved the selected task in this case. |
| address | The addresses entered. Separate multiple addresses with a comma or semicolon. You can also take the address from a variable by writing {nazevPromenne}. | |
| Organizational unit | unit selection | Direct members of the unit. Subordinate units and the manager on their own are not included. |
| From variable | dynamic user list variable | All users in the variable. |
| Role | role selection | All users with the role. |
Users without an email address are skipped. If no recipient remains, the email is not sent, but the task is still completed.

Email language
Each recipient gets the email in the language set for them in TAS. Recipients with the same language receive one shared email. The text uses the subject and content in the recipient's language. If they are missing for that language, the default subject and default content are used.
For the Email recipient type, an External language field appears. It sets the language for addresses that do not belong to any TAS user and for users with no language set. The Default option uses the default system language.
Variables in the subject and content
Variables are written in curly brackets, for example {destination} or {CaseName}. When the email is sent, they are replaced with the variable's display value. Text lists are shown in the recipient's language. An unknown variable stays in the text exactly as written.
Besides template variables, the Insert variable dialog offers system values, for example:
| Value | Content |
|---|---|
{CaseName} | Case name. |
{CaseLink} | Link to the case. |
{CaseOwnerName} | Name of the case owner. |
{CaseNotes} | Case notes. |
{TaskName}, {TaskLink} | Task name and a link to it. |
{TaskDeadline} | Task deadline. |
{FrontendLink} | Application address. |
To insert a variable into the subject or a header value, use the {} icon at the end of the field. It offers text and number variables.
Overview, notes, history and attachment snippets from the Insert snippet button are only expanded in print reports. In a sent email they will most likely remain as text in curly brackets. To put notes into an email, use the
{CaseNotes} variable.Custom headers
Custom headers are useful, for example, for sorting mail on the recipient's side or for integration with another system. Rules:
- the name must start with
X-and contain only letters, digits and hyphens, - the name and value are mandatory and must not start or end with a space,
- headers such as To, Cc, Subject or Reply-To cannot be set.
If you turn off Add custom headers (X-headers), the headers are not saved.
Send test

The Send test dialog has Email and Subject fields, both mandatory. The subject is pre-filled with the subject in your language. The Send button really sends the email, with the content in your language and with the custom headers. Only an administrator can use this feature.
The test email shows how the content looks, but variables stay in curly brackets because the test does not run in any case. You will only see the actual values in an email sent from a case.
When the email is sent
When the task's turn comes, the On start calculations run, the email is sent and the task is completed. This means On start calculations can still modify variables used in the email. If sending fails, the error is written to the log and the task is still completed. You can find the status of sent emails in the email queue in administration.
How to set up a rejection notification
In the sample template "Travel request", the Notify the traveller task sends a message to the traveller when the manager rejects the request.
- On the Email tab, set Recipient to From variable and select the Traveller variable.
- Set Reply-to recipient to Task supervisor and Copy recipient to Case owner.
- Type text into the Subject field and use the {} icon to insert
{CaseName}. - Write the message in the content and use the Insert variable button to insert the manager's comment and the link to the case.
- Use the Other language variants link to add the subject and content in Czech.
- Click Save.
Related: Task types, Instructions, sections and testing a task, Email queue.