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
Password retention policy
AyMINE pays great attention to password protection so that the system meets the requirements of the ISO 27002 cryptosecurity standards
- Global rules
- Rules for user passwords
- Rules for password communication
- Management Security Rules
- Standards adhered to
- You may be interested
General rules apply to all passwords
Global rules
Passwords:
- Never stored unencrypted.
- If it is not necessary to use it, algorithms are used that do not allow the password to be determined, only to verify
- If unencrypted passwords need to be used (typically to authenticate the system to other services, such as communication gateways), the passwords are stored securely outside the encrypted passwords so that it is not possible to obtain both by hacking one system.
- Passwords are never transmitted through unencrypted channels
- Internal encryption passwords are never global, but are always related to a specific user and purpose.
- AES-256 level mechanisms are used as a minimum for encryption.
- Passwords are stored in such a way that they cannot be retrieved or reconstructed from backups, source codes, or exports (e.g. by dump the database, by hacking the system)
- All operations in which the password is used are logged. The log is kept so that it can be detected if it is tampered with.
Rules for user passwords
User passwords do not need to be decrypted. Therefore, only control hash codes are kept that make it impossible to retrieve the password in any way. In addition, the system requires the use of a secure password.
Rules for secure password
- At least 8 characters from two groups:
- Uppercase letters
- Lowercase letters
- Digits
- Special characters
Rules for password communication
- The system never sends passwords. It only sends links to pages that allow the password to be changed.
- The system never allows password changes without a two-factor user check.
- The system always informs the user if his account is handled by the administrator. It is not possible to change the user's security settings and the user is not informed by the other way (by email). In particular, the administrator has the ability to set a new password for the user, but the user is always informed by email; the administrator has no ability to influence the sending of an information email.
Management Security Rules
The system management is designed in accordance with the requirements of ISO 27002.
Physical Security
- All physical infrastructure is located in data centre premises complying with the requirements of ISO 27002.
- Neither the data centre administrator nor anyone else with physical access rights to technical equipment has access codes that would allow access to stored passwords of clients.
- If the physical devices on which the system is operated, or which store system backups, are used by unauthorised persons, they cannot obtain stored passwords.
System Access Rules
- All assets on which passwords are managed are under the direct care of the system administrator
- All access to the infrastructure that processes passwords is managed – access is documented and records who and when accesses the infrastructure are recorded.
- The system creates an independent password usage log. The log is available to the client on request (from the use of passwords it is possible to track employee data, therefore the log is not freely available).
Code management
- Code that runs in the perimeter where data is managed is audited and must not leave the administrator's technical resources
- All code changes are audited
- The system is secured by technical means to identify code changes.
Manage the passwords themselves
- Passwords are never transmitted by any physical media
- The administrator never receives, transmits or processes client passwords – passwords are always entered by the clients themselves and are encrypted immediately after entering them. Therefore, the system administrators never see the clients' passwords, nor can they be in their electronic or other communications. All passwords are entered exclusively in an environment accessed by a worker who knows the passwords.
- Passwords cannot be displayed by the system to an unauthorised person.
- Password protection is implemented in a two-tier way – this means that obtaining a first-level password does not allow decrypting stored information, which is encrypted in a second-level password.
Unauthorised access protection
- System supports access audit and permissions
- If clients have any passwords on the system, the system requires a two-factor login from all users
- System logs both user access and unsuccessful access attempts. In case of repeated unauthorised access, the system blocks further attempts.
Standards adhered to
The system meets the requirements to be used by companies meeting the standards:
- TISAX
- ISO 20000
- ISO 27000, namely ISO 27002 (replaced the older ISO/IEC17799 standards years ago)
- GDPR
You may be interested
System permissions of AyMINE framework
System Permissions of Task Control Module
System Permissions of Order Management Module
System Permissions of Persoalistics Module