Role Groups and Teams

User Modules

Task, project & quality management
Contacts and directories module (CRM)
Web management and automation
Human resources
Products, assets and sales

Technical Modules

Sabre plugin module
Enterprise Architect connector

System Modules

The AyMINE Framework Module
System Management

Give us contact

Do you prefer to ask us directly?

Call us +420 605 203 938 (the Czech Republic)

or use this contacts

Role Groups and Teams

AyMINE uses groups to organize users into groups that match the organization's breakdown and allow for joint management.

Video guide on how to set up roles and teams is here

Users and other groups are assigned to groups. This allows me to divide groups into properties

What applies to all groups

  • A group gives users the rights assigned to it
  • A group inherits the rights of a group from the groups it is assigned to
  • A user who is in a group is simultaneously in the group to which the group it is assigned. (A group assignment is thus a transiently inheritable property.)

Group Types

Although user groups don't seem to be very different at first glance, there are significant differences between them

General Group

A group without a specific specification is created by administrators to set up the rights to use the application


A team is a group that has a manager. By being a group leader, a manager gains rights over team members. Specific rights may depend on the system modules:

  • can assign tasks to members of his team,
  • can move tasks between members,

Teams should correspond to the organizational structure of the company. But a team can also be a project team, i.e. created only temporarily.


A role determines a person's job status. It does not in itself give a member new rights, but is used in the system:

  • standard tasks are assigned to a role,
  • decisions are directed to roles,
  • roles are shown in the user's description.


Roles do not form a hierarchy

There are many hierarchical objects in AyMINE. Information, tasks, and much else can "disintegrate" into partial information, tasks, etc. This creates a tree from more general to more detailed. System groups and roles, however, are not hierarchical. They have ancestors and successors, they can have more of both – mainly ancestors.
The sense of the ancestor is also not that it is a more general group, but that the group inherits rights from it. And it can inherit them from more other groups. This is not the logic of the tree, nor are the links.

Because roles do not form a hierarchy, they do not have a tree view in the list.