AyMINE – Technical documentation
Modules
Integration with ERP Abra Gen
Task, project & quality management
Manager approval with the task report
Why some data can't be deleted
GDPR and record of qualifications
Qualification of user or contact
Right to Manage Qualifications
Adminitration of areas, projects, calendars
Failure Analysis for an Individual Property of a Component or Process
FMEA – Probability of Detection
FMEA – Probability of Occurrence
Task, project & quality management
Administration of the Task Management Module
System rights for the task management module
Improvements and Preventive Measures
Methodology and Quality Management systems
What a methodology / QMS consists of
Problems, tickets and their management
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
Management of responsibilities - RACI Matrix
Objects related to the task pattern
Contacts and directories module (CRM)
Address book list and management
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 and roles
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
Manage the Property & Business module
Why are the Quality criteria usefull
Received order for goods or services
Managing Finance
Metrics and Measurements
Work summaries from generated data
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
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
Message with the outside world
Public Client
Public Client is a special type of account designed for accounts of users who do not know each other.
- What is a public client
- Who is Public Client for
- Data protection within a public client
- Super administrator options for public client
- What settings are needed for the public client
- Setting up public distribution lists
What is a public client
This is a special type of client - the setting is done by the super administrator in the client administration. It limits the rights that clients have and changes the scope of functionality that is available. The exact changes in behavior are dependent on the individual modules.
The public client is designed to fully comply with GDPR requirements.
Under system administration for public clients:
- Users only see those users with whom they are in a common group.
- Users cannot get rights that would allow them to see across all activities
- Public Client has separate administrators for separate groups who cannot give themselves rights beyond their space.
The client administration is written here.
Who is Public Client for
Public Client is for:
- Affiliates with branches that operate predominantly on their own
- Non-profit organizations with multiple users where users work together in their own group but don't share information about each other
- Churches where individual churches and groups have members but personal data outside churches is shared limited
- Sports associations with clubs
A special type is Public Client for free or individual accounts. Within this client, users can use their own shared space and connect with those they know and exchange contacts with.
Data protection within a public client
Data protection has a similar logic to that of an ordinary client, but with a limitation of the system administrator's right. Administrators within a public client don't have available features and views that allow:
- See all users
- See and manage all areas or projects
- See other gateways than those they personally manage.
- No advanced metrics and statistics available
Thanks to these limitations, virtually all functions of the system are available, but always in a limited range.
Super administrator options for public client
The super administrator has an overview of users across the system, but has no access to the data that the users have in the system. The super administrator thus has the option of e.g.
- Create a data environment for a new branch, choir or section.
- Block user account,
- Move registered user account between branches or congregations
The role of super-controller is performed by a worker authorized by the personal data controller within the scope of the processing contract
What settings are needed for the public client
Settings for communication in accordance with GDPR
- Account must have established email address
- The account must have an address set to a page with information on the protection of personal data and its management. You can create the page directly in AyMINE, or link to the organization's website.
- A directory with contacts visible to users of all branches can be created. (It is not necessary, shared contacts can also be in the directories of branches or congregations)
I don't know.
Setting up a branch / congregation
Each branch
- Has its own directory with contacts visible only within the branch
- Has created groups of addressees for internal communication
- May have groups to communicate with the public
- Must have at least 1 internal account manager. This user can see all users and contacts within the branch/congregation directories and can fully manage them. It can open and close user accounts with access within a branch.
Setting up public distribution lists
The public distribution list allows people to manage what information they want to receive independently and in accordance with the GDPR. You can provide different information channels and users choose which ones to subscribe to. Information is always sent along with a link where they can change their settings.
Correct settings
- A specific directory is always used for public communication. It must have completed public data.
- Individual information channels are entered as contact groups. For a group to be public, it must have public data (name and description) entered.
- In addition to public groups, it is possible to have non-public groups - it is not possible to use a mass message, or to subscribe to them publicly or unsubscribe from them
- Each section or congregation can have its own distribution lists. Information seekers can see the information channels that are made available to them. They can also be from other congregations, headquarters or the seinorate (depending on the type of user).