AyMINE – Technical documentation
sys
- Translations
- System Management
- User Administration
- System User
- Documents and files
- System Groups and Teams for rights settings
- Record Relationships
- Client
- Dashboard
- Public link to the document
- Client settings
- Revisions and comments
- User administration
- Copying and moving files between objects
- Object location on the board
- Additional functions with files
- Client items
- Picture presentation
- Secure login to the sytem
- Configure gateways for external messages
- Connecting users to VOIP PBX
- Call directly from CRM
- Send SMS directly from CRM
- Formatted texts in the application
- Secure business communication
- System Configuration
- User Processes
- Processes in use
- Message with the outside world
- Email messages
- Relation types
- Securing posts and internal discussions
- Recent Files
- Crypto Wallet
- Electronic sign even on mobile device
tsk
- Required qualifications
- Package definition
- Phrases and terms
- Data Area
- Test
- Risk
- Task
- Business event
- Task, project & quality management
- Records and protocols
- Directives and Policies
- Events
- Risk Pattern
- Information
- Meeting
- Problems, tickets and their management
- 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
- Project definition
- Activity log
- List of event instances
- Task patterns saves work and improve quality
- Methodology and Quality Management systems
- My Tasks
- Task planning both in project and daily business
- Project Team
- Events and meetings
- Sample tasks and methodologies of the area
- Events and meetings
- List of event instances
- Client Settings
- Processed objects
- Mark patterns
- Manage your marks
- Region / project / methodology
- Personal calendar
- Objects of decision making
- Event activation buttons
- Objects affected by the problem
- Variant decision-making
- Recorded activities
- Self-Reminders
- Assigning a new task
- Objects related to the task pattern
- Effect of the task on the right to modify the attached object
- Level of Competence
- Manager approval with the task report
- Requirements waiting for you
- Notification events
- List of business areas
- Qualification of user or contact
- Activation buttons
- Why some data can't be deleted
- Starting events
- Qualification of user or contact
- My projects
- Objects processed in the task
- Project
- Reminders and Messages
- Notification events
- Objects of decision making
- Starting events
- Sample tasks and methodologies of the area
- Activation buttons
- Records managed by a project
- Timesheet
- Project role
- What makes up the methodology / SMJ
- Drag & Drop between records
- Location
- My areas
- Kanban Task Overview
- Personal Task
- Internal helpdesk
- Customer Care Centre
- Project baseline
- Return project plan by baseline
- Project Schedule
- Type of tests
- The person responsible for the task
- Deals / Contracts
- Customer Service Response Generation
- 8D report - tool for problem resolution
- 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
- Notice – example of use
- FMEA criteria for detection evaluation
- FMEA system functionality analysis
- Methodology how to conduct FMEA
- FMEA analysis of the failure occurence
- Analysis of the FMEA Severity
- FMEA Analysis
- Management of responsibilities - RACI Matrix
- RACI Matrix for Project
- Improvements and Preventive Measures
crm
- Directory or people and companies
- Address books
- Contact per person or company
- Order overview for customer groups
- Customer Order Overview
- Message patterns
- Quickly available contacts
- Contacts and directories module (
- Address book list and management
- Privacy policy
- Groups of contacts
- System Permissions and CRM Module Settings
- Contracts
- Send bulk messages in compliance with GDPR
- Bulk email footer
- Bulk Emails
- Partner in a contract
- Unsubscribe and set preferences
for bulk mail - How to correctly forget a person's details
am
- Product Categories
- Shared analytical model accelerate your project and development
- Products, assets and sales
- Products and Goods
- Tendering and purchasing
- Product Supplier
- Product status and change
- Project Goal
- Business Offer
- Recalculate bid
- Pricing
- Pricing – volume discounts
- Offers summaries
- Order Reports
- Quality criteria
- Creating and processing orders
- Product or Product Property
- Why are the Quality criteria usefull
- DFEMA - FMEA of the product design
- HARA for product
- Offer and Price Access Rights
- Product Units
- System order status query
frm
- List of records
The AyMINE Framework Module- AyMINE releases
- AyMINE – Initial advice
- AyMINE Modules
- Object locks
- Configure how your system looks and works
- Filtering in the list of records
- Icons in AyMINE
- Deleting
- Your main dashboard
- Object lists
- More about how the system works
- Object detail
- Private notes and tags for objects
- ClipLink
- Gestures and keyboard shortcuts
- Drag & Drop between records
- System rights
- AyMINE (C) 2020
- Gestures and Keyboard Shortcuts
- Password retention policy
- framework user rights
- AyMINE — Windows Application
- AyMINE — Tips for Mobile Usage
- Overview of Modules and Record Types
hr
- Human resources
- Worker
- Human Resources module security
- Personalistics – User Permissions and roles
- Manage department / division data
- Synchronizing staff and system users
- Responsible HR Manager
- HR module role
- Registration of job seekers
- An overview of your staff
- Digital Personnel Archive
- Job Position
- Worker overview
System User
Representation of a system user - present, past and future.
System user accounts include both actual and virtual system users.
User's Working Status
Forgotten User
Users who no longer use the system (because they have already left the company) can usually not be deleted because there is a lot of other information attached to the account - e.g. they are the authors of the decision or their qualifications are proof that the work was done by qualified staff.
Only a user who has been deleted before can be forgotten.
The GDPR website (/doc/en/sys/sysUser_gdpr) is more concerned with ensuring GDPT compliance and meeting legal information obligations.
Deleted User
Deleted User is not forgotten: Deleted account is moved to the trash, it is not possible to work with it, but e.g. worker's name remains unchanged. E.g. Tasks will continue to show the real name of the staff member.
deleting the account will delete the user's personal notes.
Blocked user
Blocked is a user who for some reason cannot temporarily log on to the system. Account can be blocked automatically (based on security analysis) or blocked by administrators.
Account blocking partially prevents use within the system, blocked user e.g. is not able to send a message. Blocking is therefore suitable e.g. in case of long-term unavailability of the worker (e.g. on maternity leave)
Unblocking the user must always be done by the system administrator.
Special user accounts
In addition to regular user accounts, the system supports several special accounts
Virtual user
Virtual user is used to document operations that have not been performed by the real user, but are stored in the history. It is used e.g. to document actions that have been performed by clients on the customer portal, etc.
Virtual user can never log on to the system.
External "padded" user
A padded user is used when you need to assign tasks or responsibilities to an external company or worker who does not work with the system. For example, when you plan responsibilities in the RACI matrix within project.
For a padded user, it is possible to document qualifications as well as for an internal user - it is available for data management in the same way as an internal user, but it is not possible, for example, to include it in a discussion or to send it a message. (However, it may be a participant in a meeting, although in this case it is preferable to use an external contact of a real person.)
A padded account is managed by the project manager or the area where it is used. A padded account can never be logged into, it is not possible, for example.
External Administrator
An external administrator is a user account of system administrators within the data space of a particular client. Most of the system administration can be performed exclusively within clients, and if the client uses external administration support, the administrator must have a dedicated account to do so.
The external administrator is marked in the reports and is excluded from accessing protected corporate data. Even if it has a high-privilege account, it is not possible, e.g., to include it in the encrypted communications group. This prevents it from misusing its privileges and prevents it from being misplaced.
Note: For non-confidential common data, its access is controlled by the normal privileges system, and it is up to the permission of the area manager or the project to allow it.
User activity tracking
For active users, the system monitors whether you are active. Generalized activity information is visible to other users. The information prevents them, e.g., from assigning a task to a worker who has not been using the system for a long time. (The task could then remain unsolved.)
When working at a home‐office or otherwise remotely, the system provides user activity information to co‐workers, who can count on the worker to react.
Activity is distinguished in several stages:
-
In the last 10 minutes, the user has actively performed an action (is actually working – it is not "clicking screens")
-
The user is actively logged in, but is not working
-
The user has not been effectively working for more than an hour (is not using the system)
-
The user has not been accessing the system for a long time (more than 2 days) - it can be assumed that he is on vacation
-
Users currently working with the system are shown active
-
Unknown status is for users who may have AyMINE running in the background (or on mobile) but are not currently working with it.
-
Unavailable are workers who are reported.
Activity Tracking in GDPR Context
User activity information is shown only to people for whom it is important in terms of their own work - executives and co‐ colleagues. It is therefore made available on the basis of legitimate interest.
Information cannot be evaluated retrospectively.