AyMINE – Technical documentation
Interfaces to other systems
Enterprise Architect Connector
CalDav, WebDav using Sabre
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
- Configure gateways for external messages
- Message with the outside world
- Email 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
User Administration
User Administration Information
- User Statuses
- Creating a user account
- Automatic registration of members of associations and organizations
- Permission Settings
- Password Changes, if any
- User Rights Settings
- May interest you
Warning: This page is intended for administrators. Other staff members do not have access to the information described here.
User administration includes steps:
- Create User Account
- Set Permissions
- Password Change If Possible
User Statuses
A basic overview over a user provides a status. A user account can be in several states:
- Active User who has the ability to log in and work on the system
- Invited A user has been sent an invitation to create an account on the system, but he has not yet created one (he has not used the invitation). Warning, invitation is valid max. 48h. If a user was invited more than 2 days ago, he or she remains invited, but cannot activate his or her account without re-sending the invitation.
- Blocked is a user account if it has been blocked by the administrator or the user has repeatedly logged in unsuccessfully. The user does not have the ability to unblock his or her account independently and must ask the administrator. Unblocking is possible within the user's detail, or even collectively in the user's overview. By default, users are blocked if their accounts were created without sending an invitation.
Blocking the user does not remove any of his/her personal and private information from the system, and after unblocking the account returns to the same state as before it was blocked
- Deleted The account of the user who has ceased activity. The account cannot be logged in.
Deleting the account deletes all of the user's personal information from the system (e.g. personal notes on objects), user settings, and other personal data. However, the account is not anonymized and it remains possible to identify which activities the user has performed.
The deleted account can be restored, but it is not possible to restore the deleted personal information.
- Forgotten The account has been anonymized and personal data has been deleted in accordance with GDPR
Creating a user account
You create an account by creating a user. You need to enter the user's email and phone number.
The user gets a registration email asking them to log in and fill in their email. The registration email is only valid for 2 days, so do not send users emails if you do not know when they will register.
Automatic registration of members of associations and organizations
The system also allows automatic registration, where you can give users a registration code with which they can create an account themselves. The registration code can be assigned by the system administrator and is valid for a specific company.
We recommend using the registration code where there are a large number of users and it is not organizationally appropriate to take care of access centrally. Typically, the use of the codes is used to connect members of associations, associations and political parties. In their case:
- Create a system group for each unit (section, center, one cell) and enter a login code for the group
- The group manager can see the code in the system (but by default does not have the right to change it)
- The group manager shares the code with the members.
- When a new member registers with their group code, it will be automatically included in the group, so no further administration is needed.
Note: The same use of registration codes in a common company or small group is potentially also possible, but does not usually make sense.
Permission Settings
You need to assign permissions to the user. It should be assigned to a specific role. Permissions are given to the user based on the groups to which they are assigned.
Password Changes, if any
If the user forgets the password, administrators can send an email to the user, upon request, to reset the user's password themselves. The user cannot generate the email themselves for security reasons (thus there is no risk of access to the system if someone misuses the user's email.)
Administrators can directly set the user's password. The user can use it without a registration email. When changing the password, the user is notified by email that their password has been changed by the administrators; however, the new password itself is not sent by email.
Access rights for outside workers
If your company works with a worker who has his own account (e.g. a free account), it is not possible for this account to be used to access the company environment and it is necessary for the user to set up his own account.
User Rights Settings
System rights
AyMINE never assigns system permissions directly to the user. Permissions always refer to a role or group of people. Therefore, you only set the user's system rights by assigning them to a group or by assigning them a role.
Rights arising from an object relationship
The user can obtain rights based on their role to a specific object (e.g. the right of the meeting manager to terminate the meeting). These rights are not administered by the administration, but arise from working in the system.
Automatic administration and manual startup option
System rights can be set automatically for the worker based on the HR manager's administration – They are set automatically after a change in the employee's contract or status (e.g. after the termination of his last employment contract).
For more information on administration, see the employee's documentation.