You can set desktop or web rights for every user in Quant, which affects what the user can access. You can also assign users to user groups and control desktop or web rights at the user group level, so you don't have to set the same rights for each user individually.

In this manual you will learn:

• What are user roles for and which ones make sense to use?
• What are user groups for?
• What is a system group?
• How do you create a user group?
• How do you set rights on a user group?
• How do you make a specific item (e.g. a project) available only to a specific user group?
• What are the access levels and what do they mean?

User Roles

Quant has historically offered several user roles under which you can create users. These roles have now been replaced by more flexible user groups. We recommend using only the roles of Category Manager and Store Manager, or Suppliers (for the purpose of listing or displaying a planogram with only supplier's products), and setting all differences between users up in a user group where you can freely assign users and sort them according to their competencies. The Robot role is created only for the purpose of setting up Rest API automated tasks.

Category Managers

These are users who have access to both the desktop application and the web. Basically, these are head office workers who can create planograms, floor plans, manage products and more in Quant. You can then restrict their rights and categorize administrators by competency.

Examples:

• Users who manage floor plans - have access to the Store Editor to create store floor plans or to reports related to floor plans.
• Users managing planograms - have access to the Project Editor or Planogram Editor to create planograms or to reports related to planograms.
• Users who need to monitor and evaluate various sales indicators, therefore they only need to access the analysis.
• Users who are in charge of the product library - they can add new products, make changes to them, etc.
• Users managing the category hierarchy.
• Users managing communication with stores - creating e.g. blog content - blog, polls, or forms.

Of course, the Category Manager can also be a general user who has access to everything. It depends on how you set desktop and web rights for this user.

Store Managers

These are users who only have access to Quant Web, where they can see content created for them by Category Managers. On the web, they can see their stores that they manage, the planograms for that store, the products placed in the planograms, etc. They can confirm the implementation of the planograms. According to the rights settings, they can also e.g. fill in store checks, enter tasks in task management, etc.

User Roles

For a detailed procedure on how to create a new user, see the Creating a User manual.

User Groups

User groups allow you to divide users into groups, so that you can set rights for them in bulk and restrict access to specific items if necessary. Unlike user roles, user groups are fully configurable and you can create as many as you want and set the rights as you need them.

System Groups

Quant creates some groups automatically - groups by user roles and the Everyone group. These groups also automatically contain the created users corresponding to the group, the Everyone group includes all created users in Quant regardless of his user role. You can recognize the groups automatically created by Quant by having the System Group checkbox checked.

System Groups

Creating a new group

Click on the New button to create a new user group and set its properties on the right.

Create a new user group

Setting rights for a group

You can restrict desktop or web right to a group of users so that users within the group can access only the sections they need to do their work in.

Desktop Rights restrict access within the Quant desktop application. In Web Rights, you set where the user will be able to access the Quant Web site.

For example, if you have a department that is only responsible for floor plans, you can include these users in the same group and then select only the floor plan related sections in desktop and web rights. This way they won't be able to access projects and edit planograms, for example.

Setting rights for a group

One user can belong to more than one group. If the permissions are set differently on each group, the user will see the section/feature if it is enabled in at least one of the groups to which the user belongs. Similarly, if a user has rights set in the Users section and also belongs to a group which have the rights set, everything that is enabled in at least one place will be made available to him/her.

We recommend to manage the rights at only one level - either at the user level or at the group level. If you set permissions at both levels, they may interfere with each other. Therefore, if you decide to go down the route of creating groups, be sure to clear the rights at the user level.

Resetting the rights of a user

Assigning a user to a group

Making specific items available

In some cases, it is not enough to restrict access to an entire section, but you need to split users so that, for example, each user group manages its own project and at the same time users from different groups do not interfere in each other's work.

In Quant, you can set rights for a specific item in most places where it is appropriate. This can be for a specific project, store, category, analysis criteria saved in the library, etc.

This is set in the Access line, which can be found in the basic properties.

The default setting for any particular item is that everyone has access to it and can edit, delete, etc. Thus, in the Access row, the Everyone group is set at the Owner level.

Access settings for a store

Larger companies may have their stores divided into several store groups (brands). Consequently, the department managing the planograms is also divided into several smaller departments, each of which is in charge of a given group in its own project. To avoid unintentional mistakes and employees interfering with each other's work, we set up access for groups of employees managing a given store group on each project.

1. Create a user group that includes all users who are in charge of planograms for the same store group and set the necessary rights.

Setting up a new group

1. In the Project Properties, set the Access property to this group and delete the Everyone group.

Access to projects 1

Access to projects 2

If you make settings like in the above images, only users from the MixMarket group will be able to see and edit the MixMarket Planograms project. Other users will not see the project at all. It is also possible to allow other users to see the project but to not save changes in it. In this case, you must assign the Everyone group to the Can Read access level.

Access Levels

Access levels allow you to set the extent to which users can interfere with editing, saving changes, changing access rights, or deleting. The different access levels are described using an example project.

• 
  
  • Owner: The user can open, edit, save, delete the project and also change the permissions in the Access line.
  • Can edit: The user can open, edit, save the project, but does not have permission to delete the project or change access rights on it in the Access line.
  • Can Read: The user can open the project, but cannot save their changes. He or she cannot delete the project and does not have permission to edit access on the project.

Access levels