AyMINE – Technical documentation
Modules
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
Adminitration of areas, projects, calendars
Region / project / methodology
Change management process in a project
GDPR and record of qualifications
Qualification of user or contact
Right to Manage Qualifications
Task, project & quality management
Administration of the Task Management Module
System rights for the task management module
Methodology and Quality Management systems
What a methodology / QMS consists of
Collaborative Resolution of Multiple Problems
Customer Service Response Generation
Incident and Quality Issue Management
Objects affected by the problem
Problems, Incidents, Helpdesk Tickets
Return project plan by baseline
Sample tasks and methodologies of the area
Effect of the task on the right to modify the attached object
The person responsible for the task
Working procedure – task definition
Objects related to the task pattern
Contacts and directories module (CRM)
Order overview for customer groups
Contacts and directories module (CRM)
System Permissions and CRM Module Settings
Send bulk messages in compliance with GDPR
How to correctly forget a person's details
Unsubscribe and set preferences
for bulk mail
Web management and automation
Receiving a message from the web
Human resources
Personalistics – User Permissions
Human Resources module security
Manage department / division data
Overview of Personnel Information for pracov# Employment Contract
Synchronizing staff and system users
Products, assets and sales
Received order for goods or services
Finance management
Metrics and Measurements
Technical Modules
Sabre plugin module
Enterprise Architect connector
Database link to Enterprise Architect database
Enterprise Architect connector
System Modules
The AyMINE Framework Module
AyMINE — Tips for Mobile Usage
Configure how your system looks and works
Gestures and Keyboard Shortcuts
More about how the system works
Private notes and tags for objects
Overview of Modules and Record Types
Filtering in the list of records
System Management
Securing posts and internal discussions
Additional functions with files
Copying and moving files between objects
Files (documents) linked to the object
Formatted texts in the application
Gateway settings for external messages
IMP gateway settings for email communication
Internet Call Gateway Settings
Human Resources module security
The module is developed from the ground up in accordance with GDPR legislation and data protection standards of large organizations
- Can system administrators see the data?
- System administrators can see data about users!
- Is the system fully compliant with the GDPR?
- The worker expressed suspicion that someone had accessed his data
The issue of security and compliance with GDPR and legislation in general is central to the Human Resources module. AyMINE was created at a time when GDPR was already in force and was born by an expert on GDPR (among other things, he was responsible for meeting GDPR requirements in large organizations). At the same time, the whole system is built to protect data – not only human resources – as much as possible. Therefore, Human Resources used the whole concept of the system, which puts security first.
Can system administrators see the data?
They can't. Until an employee has one of the above-mentioned roles, he or she is not authorized to look at the data.
Access control applies not only to administrators within the organization, but also to system administrators. Data from the Human Resources module can never be looked at by any system administrator, because it is possible to work with it only within the account of your organization. System administrators do not have an account of your organization.
System administrators can see data about users!
Yes, system administrators can see the system accounts overview, but this is not the data of the HR module. The system account contains:
- First name (required)
- Last name (required)
- Email (required)
- Phone number (optional)
This data does not have to match the data in the HR module. The data is needed for the administration of the system – e.g. to allow system support to respond to a query or problem of the user.
Is the system fully compliant with the GDPR?
Yes, it is. From the GDPR point of view, not only the protection within the HR module is important, but throughout the system.
Both the system itself and its operation are compliant not only with the GDPR, but also with other legislation. Even if you are using a system hosted as a service, the system complies with all security requirements.
- The data is located in the European Union
- The system can forget a worker, but at the same time store the data necessary to preserve for reasons of legislation or legitimate interests of the organization
- The system allows a worker to verify what data the organization holds about him or her. As part of the work overview – the worker's dashborad has a view of this data, but cannot change it (He must report the change to the HR officer)
The worker expressed suspicion that someone had accessed his data
The system – as well as the basic registers of the state – records each individual access to the HR folder by the HR officer. The worker can therefore check whether the HR officer has accessed the data.
The system does not individually register the approaches of the payroll accountant. It is not about access to individual data, but about mass data processing mandatory by law. It is registered as a mass access, which is not displayed to the workers.