Modules

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.

Modules

Technical Modules

System Modules

Let us know what you're looking for

Do you prefer to ask us directly?

User Administration

User Administration Information

User Statuses