Authorization Models

Note! This guide is developed for the MKG004 software. If you are using MKG5, the description of the operation may differ here and there from your environment. We aim to create a product-specific description for this topic in the future.

Below, the characteristics of two authorization models are discussed. It is possible to combine both models.

Simple Authorization

• All users are members of the 'All' group and by definition have access to everything.
• Authorize with the 'Module Authorization'.
• Authorization is done by indicating where a user does NOT have rights.

Advantages

• Relatively quick to set up.
• Less in-depth MKG knowledge required.

Disadvantages

• Options such as 'View Only' are not possible.
• Copying to a new user must be done at the user level. If no access is given in a group, the user also has no access.
• Users automatically gain access to a new module in MKG.

Extensive Authorization

• No user is a member of the 'All' group. Therefore, users have no rights by definition.
• Authorize with the Authorization module and by using tables authorization.
• Authorization is done by indicating where a user or user group DOES have rights.
• Authorization can be at the user and user group level.
• When adding a user to a user group, the rights of this group will be transferred to the user.

Advantages

• Possibilities to assign all types of rights within MKG.
• A new user can easily be added to different groups. When access is given in a group, the user also has access.
• Users must obtain access to a new module within MKG.

Disadvantages

• More in-depth MKG knowledge required (how the tables are structured, etc.).
• Setup takes longer.
• More likely to require optimization/maintenance afterwards.

Authorization Management: index