Right structure

The access to data in the database of LOGO CRM is handled by a smart and constantly bettering right structure. With over 100 rights, each individually selectable, you have the chance to determine very specifically, which users can see what about your customers in LOGO CRM. The different users are also handled with the right structure. This can influence the creation of certain elements or even the right to access certain modules.

In order to ease the process (especially being required to give each user his rights separately), you can create right bundles and assign them to an EOS-Function. For example, employees from the sales department usually have the same rights, which documents they can see and edit, what appointments and tasks they can see. To do that, first you define a right bundle called “Sales Department”, which you can now assign to the right employees. This is called “Rights through function”.

Additionally there is a “Right per user”. For every user you can ad or remove rights, differing from his right bundle.

The right structure in LOGO CRM is a powerful module. The settings in it have a big impact on how users are able to work with the system. Errors can lead to problems, such s employees not being able to see modules they need for their daily work.

LOGO consult with assist you at the start of the project and throughout with the proper construction of your right structure.

In the administration area you will find the table “Rights”. Shown are the rights of the current user at first. The column “Right” shows the description of the right, on the right of that you find the rights through function and the last column shows rights per user.

Above the list showing the rights you will find an area where you can see the different right settings, export the right settings and change them.

Here you also experience the splitting of user rights and function rights. The function rights can be select from a drop down menu, the user rights from the EOS.

The button “Export all” creates a .csv file, which contains both rights by function and rights per user. This is helpful to see, which function has which rights.

LOGO CRM has different types of rights for different areas.

In some areas a simple yes/no right is enough. Here, the super user only hs to decide if a user can use a function or not.

Examples are the creation of general reports or the access to the administration area. If you wantto grant a user access to the administration area, the selections are the following:

Other rights are defined within the company structure. For example, what kind of tasks an employee/a user group is allowed to see. Only their own, the team's, the departments or all from the branch? Here you have to make a selection from the company structure. Depending on your settings it could look like this:

Some rights have the setting “All of customer”. This means, an employee can access all elements from a customer for whom he is in charge of. This can, for example, be selected in “Edit documentations“:

In general, a user has more rights the higher he is sorted into the EOS-Tree. Access rights can't be restricted from top to bottom. From bpottom to top - for example an employee in a team, under a department under a branch under a country – access and edit rights are configurable in great detail.

You can – for example – allow a user to see every customer and all documents of his branch, but only see the appointments from his team. He can edit all documents from his team but only may edit appointments that are his own.

Now functions are given their proper rights. This process is done in close work with the department heads. The basic principle here is: Super users have a big variety of rights while normal user have just enough rights to do their job correctly.

The explanation and listing of all rights would be tool long for this short guide – there are over 90 of them.

Usually, right bundles are worked out in a workshop together with the super users, and after that slight modifications are made by super users.

The last step is the restriction/extension of individual user rights. But the goal should be to define right bundles in a way, only very few exception have to be made.