AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
Business excelenece
Balance Scroecards
Task & Project Control
- Helpdesk ticket - reply to customer
- Test
- Qualification of user or contact
- Project role
- What makes up the methodology / QMS
- dragdrop
- Location
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Processing time sheets
- Records managed by a project
- Activation buttons
- Why some data can't be deleted
- Starting events
- Qualification of user or contact
- task_taskobjects
- Project
- Reminders and Messages
- eventobj_raisingevents
- decision_decobjects
- eventobj_startingevents
- eventobj_eventbuttons
- Type of tests
- Deal management
- FMEA - Detection
- FMEA - Features
- FMEA Methodology | AyMINE
- FMEA - Occurence analysis
- FMEA Severity analysis
- FMEA
- Management of responsibilities - RACI Matrix
- RACI Matrix for Project
- Improvements and Preventive Measures
- Notice – example of use
- tskproblem_terminology
- 8D report
- Task Scheduling
- Administration of the Task Management Module
- Adminitration of areas, projects, calendars
- Discussion
- GDPR and record of qualifications
- System rights for the task management module
- Project Planning
- Employee Tasks
- Incident and Quality Issue Management
- Collaborative Resolution of Multiple Problems
- List of business areas
- Required qualifications
- Plan template / strategy
- Decision
- Configuration Package
- Record template
- Change management process in a project
- Task list
- Requirements
- Team Member
- Right to Manage Qualifications
- Input requirements
- Obligation
- Competencies and Skills
- Problems, tickets and their management
- Meeting
- Package definition
- Phrases and terms
- Data Area
- Risk
- Task
- Business event
- Task, project & quality management
- Records and protocols
- Directives and Policies
- Events
- Risk Pattern
- Information
- Project definition
- Activity log
- eventinstances
- Personal calendar
- Objects of decision making
- Event activation buttons
- Objects affected by the problem
- Variant decision-making
- Recorded activities
- Self-Reminders
- QMS and Task Management
- Objects related to the task pattern
- Effect of the task on the right to modify the atta
- Level of Competence
- Manager approval with the task report
- Region / project / methodology
- Manage your marks
- tskdefusertask
- Quality Management System (QMS)
- tsktask_batasks
- Project Team
- Events and meetings
- Events and meetings
- List of event instances
- moduleclientoptions
- Processed objects
- Mark patterns
- Notification events
Interprocess management
Human Resources
- hrstcontract
- roles
- Human resources
- Digital Personnel Archive
- Personalistics – User Permissions and roles
- Registration of job seekers
- Manage department / division data
- Job Position
- Worker
- Worker overview
- An overview of your staff
- Responsible HR Manager
- Synchronizing staff and system users
- modulesafety
Asset Management
- Products, assets and sales
- Tendering and purchasing
- Analytical model
- Product Supplier
- Product Categories
- Product or Product Property
- Project Goal
- Business Offer
- Offers summaries
- Recalculate bid
- Offer and Price Access Rights
- Creating and processing orders
- System order status query
- Order Reports
- Pricing
- Pricing – volume discounts
- Products and Goods
- Product status and change
- Product Units
- Quality criteria
- Why are the Quality criteria usefull
- DFMEA - Product FMEA
- Hara | Hazarad & Risk Analysis
Customer Relationship - CRM
- Contacts and directories module (
- System Permissions and CRM Module Settings
- Customer Order Overview
- Address books
- Address book list and management
- Privacy policy
- Send bulk messages in compliance with GDPR
- Bulk email footer
- Unsubscribe and set preferences
for bulk mail - How to correctly forget a person's details
- Bulk Emails
- Contracts
- Partner in a contract
- Message patterns
- Groups of contacts
- Order overview for customer groups
- Directory or people and companies
- Contact per person or company
- Quickly available contacts
Finance management
System modules
System management
- moduleclientoptions
- digiSign
- formattedtexts
- System Configuration
- Processes in use
- Client
- Public Client
- Configure gateways for external messages
- E-mails and external communication
- Email messages
- Rules for external messages
- Secure business communication
- Send SMS directly from CRM
- Call directly from CRM
- Documents and files
- Additional functions with files
- Copying and moving files between objects
- Picture presentation
- Public link to the document
- Recent Files
- Dashboard
- Object location on the board
- Client items
- Revisions and comments
- Securing posts and internal discussions
- Translations
- Record Relationships
- Relation types
- sysrole
- User Processes
- System module
- System User
- User administration
- User Administration
- Secure login to the sytem
- Connecting users to VOIP PBX
- Secure Key Wallet
Framework
- frmobjectextension
- introhelp
- introhelp_mobile
- introhelp_aplikace
- versioninfo
- releases
- AyMINE modules and basic types
- cliplink
- introhelp_settings
- introhelp_deleting
- introhelp_dragdrop
- list_filtering
- AyMINE intro
- AyMINE access security
- AyMINE Modules
- Object locks
- System rights
- introhelp_keyshortcuts
- introhelp_shortcuts
- introhelp_icons
- list
- introhelp_generalinfo
- introhelp_objectdetail
- introhelp_objectlist
- introhelp_privateobjectnotes
- AyMINE User Rights Control
- introhelp_dashboard
Management of Email and External Messages
- Corporate Email Is Not Private Email
- Correct the Perception of Email in the Company
- Priorities for a Corporate Email Application
- What the Law Says About Corporate and Personal Emails
- Proper Management of Corporate External Communication
- Managing Message Processing
- Automatically Creating Messages from Templates
- Monitoring Message Processing
- Automatic Assignment of Messages
- Use Email Effectively
Corporate Email Is Not Private Email
Most people perceive corporate email as their personal mailbox. However, this should not be the case. The real-world examples mentioned above illustrate only a few of the risks that may arise. In many organizations, email has become the sole communication channel—aside from the telephone, which serves a different purpose.

For email to function properly within a company and not create unnecessary risks:
- Email processing must be set up so that private and business messages can be clearly separated.
- Incoming messages should primarily be addressed to the company rather than to individuals. Where genuinely private messages are part of work tasks, they should be separated appropriately (see recommendations below).
- Internal and external communication must be clearly separated. (Internal communication is addressed, for example, in sections about notifications or discussions.)
- Effective communication with the outside world requires a dedicated application designed for this purpose. Standard personal email applications (including tools such as MS Outlook) are not designed for this role.
What are the priorities of a corporate email application?
Correct the Perception of Email in the Company
The vast majority of external messages that an organization receives or sends should not have a private nature. Hiding corporate communication in private mailboxes harms companies.
Whether emails support sales, service delivery, or internal business processes, they should not be private.
- Work must be reviewable—even when it takes place via email.
- Work must be measurable in terms of both quality and quantity.
- Every company should aim for substitutability and continuity of roles.
If business or administrative activities take place through private messages, none of these goals can be effectively achieved.
External Communication Is Not Only Email
Email is the most common medium, but communication records arise through various channels, and systems should be able to combine them. Besides email, common communication channels include:
- Messages through web portals – B2B portals, complaint portals, etc.
- SMS messages
- Records of phone calls
Helpdesk systems (including AyMINE) can combine such messages, and other business processes should ideally provide similar capabilities.
How to separate private messages
Priorities for a Corporate Email Application
Email systems that receive external messages should primarily be designed to clearly separate private messages (see the next section) from standard corporate communication. For commercial email communication, the system should create a shared environment so that incoming messages can be processed by anyone responsible for the process.
If messages are treated as private by default, no one else will know that a message has arrived until the recipient decides to share it. Most people already have large volumes of incoming email, making it easy for a message to be overlooked. If the recipient becomes ill or overloaded with work, processing may be delayed.
Examples of Poor Message Management
Prosecutor’s Office Audit
In 2025, a public prosecutor was dismissed for failing to process international requests for cooperation. As a result, investigations abroad concerning criminal cases involving Czech citizens stalled. The prosecutor’s office lacked a system for monitoring unprocessed messages, which delayed investigations and the seizure of assets in favor of the Czech Republic.
The problem persisted for years because email communication was not subject to oversight, and no one could detect that the work was not being carried out.
Sales Manager Oversight
A company’s sales department handled inquiries through a single employee. Over time, the employee stopped responding responsibly and failed to answer some requests. The company discovered the issue almost by accident after the employee left.
During that period, the company lost dozens of potential contracts because no one responded to incoming inquiries.
The company began contacting clients again after six months, but by then customers had already placed their orders elsewhere and had lost trust in the company. The total financial loss amounted to millions of Czech crowns.
Injury of a Project Manager
A project manager responsible for communication with a client was injured and unexpectedly absent from work for two months. Because all communication took place through the manager’s personal email account, no one else in the company had an overview of the project’s status.
The manager had always been reliable and was also a co-owner of the company, so the project had not been closely monitored by others.
Before the manager returned, the client contacted the company. Initially, the client tried to reach the injured manager directly, but later contacted the company itself. Only then did the organization realize there was a problem.
The project fell behind schedule, and the company faced significant contractual penalties and a loss of credibility. Although the client did not enforce part of the penalties due to understanding the situation, the company’s reputation as a reliable supplier was significantly damaged. Despite the client’s goodwill, the incident had a substantial commercial and financial impact.
The main issue was not the absence of oversight—if the injury had not occurred, the co-owner would likely have continued working successfully. The real problem was that the project had no risk management regarding team continuity, and project communications were not accessible to anyone else.
Corporate email and the law
What the Law Says About Corporate and Personal Emails
In the Czech legal framework, the protection of email communication is primarily addressed by Act No. 110/2019 Coll., which implements the European GDPR regulation.
Other important legal frameworks include Act No. 89/2012 Coll. (Civil Code) and Act No. 262/2006 Coll. (Labour Code).
These laws imply that it must be clearly distinguishable which emails are addressed to a private individual and which are addressed to the company. This distinction must be clear not only internally but also to the senders of incoming messages.
Legal interpretations commonly agree that:
An email address in the form of
<firstname>.<lastname>@<company>.czis considered personal data, and messages delivered to this address are regarded as private correspondence.
It should therefore be noted that:
If the sender has reason to assume that an email address is private, the message must be treated accordingly.
Separating private communication from corporate communication
Proper Management of Corporate External Communication
Limit Personal Addresses
The best solution is for employees not to use personal addresses for communication that is not private.
- Use addresses that do not represent personal data. Common formats include
jan.novak.sales@company.com,novak@sales.company.com(sometimes more complex to manage on servers), ornovak.sales@company.com. - For projects, create dedicated email addresses for official communication, such as
is-zdt-2025@company.com.
Another advantage of this approach is the reduction of spam. Email addresses are often easy to guess by both people and automated systems, either by trying combinations or by following patterns used for other employees.
Require Employees to Separate Private Emails
Message Flag
Use a private-message flag within the email system. Depending on the employee’s role and communication type, this flag may be enabled or disabled by default. In most cases, however, the default should be set to not private.
Otherwise, if the employee becomes unavailable, no one else will be able to access the messages. In practice, employees are also more likely to keep privacy protections enabled rather than deliberately sharing messages.
Shared Folder
Sharing folders where employees move relevant emails is the simplest approach and is commonly used. With properly configured rules, emails can be moved automatically.
However, shared folders carry risks: messages often lack appropriate protection and maintenance. It is not uncommon for such folders to exceed 2 TB in size without anyone maintaining them. In addition, messages must remain in the shared folder to be visible to others, even if they should logically belong elsewhere.
Replace Email with Other Communication
The most effective solution is often to replace email entirely with alternative communication channels:
- Customer or supplier portals
- Directly integrated messaging systems
These approaches are already standard practice:
- Large companies often provide only a web form.
- Companies use supplier and customer portals.
- Regular clients may communicate via integrated data connections.
Managing Message Processing
As long as emails remain in personal inboxes, they cannot be effectively linked with other records. In most companies, however, emails relate to something specific: an order, contract, project, issue, or request. Therefore, messages should be directly linked to the relevant records.
Linking Messages to the Relevant Subject
You can create messages directly from records about which you need to communicate—orders, offers, issues, or project requests. The message remains permanently stored with that record, allowing you to maintain a long-term overview of how the subject was communicated, whether by you or by a colleague whose responsibilities you later assumed.
The key advantage is quick and reliable retrieval of information. It no longer depends on individual availability, and interactions with clients become significantly more professional.
Automatically Creating Messages from Templates
Corporate messages are often repetitive, which makes templates an important tool. Although artificial intelligence partially replaces them, templates remain faster, simpler, and more cost-effective.
Unlike AI-generated content, with templates you know exactly what you are sending and do not need to review every message in detail. Data from related records—such as orders, products, or projects—are automatically inserted into the template.
Monitoring Message Processing
You can launch a processing workflow directly from the message. When the workflow is linked to the message itself, it becomes much easier and clearer to monitor progress. Key monitoring tools include:
- Assignment of responsibility
- Launching the processing workflow
- Linking the message to the relevant topic
- Continuous monitoring of processing status
- Options for personal and shared notes
- Internal discussions and message notifications
Notifications do not generate additional emails—they function through internal chat.
Automatic Assignment of Messages
Messages arriving at shared addresses (e.g., orders@…) can be automatically assigned to employees based on predefined rules. For example, a sales representative responsible for a particular client may receive the message automatically.
Communication directly linked to records ensures that agreements and commitments remain visible—even when a colleague is on vacation or has left the company—without compromising the privacy of their personal mailbox.
All messages are sent through gateways, where processing rules are configured. Each shared or private address has its own gateway. For private emails, users configure the connection themselves and never share their password with anyone.

Use Email Effectively
Follow these practical guidelines:
- Use email exclusively for communication with the outside world.
- Do not forward emails within the company—you lose visibility of how the message is being processed. Communicate internally through system tools attached to the message.
- Connect messages with the website, but avoid sending unnecessary emails from the web
- For internal communication, use discussions, notifications, or tasks.
- Create message templates so employees can send messages quickly and without grammatical errors.
- Establish a client portal so that clients can see the entire communication history. This saves a significant amount of time. Clients will no longer search for documents you have already sent, and you will not need to reconstruct what they are referring to. In practice, this can reduce communication time by at least 50%. The design of the portal may vary depending on your clients—for example, here is documentation for a B2B portal.