Edit Item Responsibility Groups

The Item responsibility groups are used to limit a user's access to specific Items, occurrences of Items or Products (here called Item-related objects). By assigning a responsibility group to an Item-related object, you can limit who can just see an object at both the Type and Occurrence Levels and who can update it. 

Setting up Responsibility groups

To use, first create the responsibility group you want to limit your item-related object to. This is done in Settings in the client (under Project and database administration → Settings → Items → Responsibility groups. Add the new  (see below).

Open

Here you can add your new Responsibility. Please note that the abbreviated version ("Responsibility") is displayed a number of places, so it is a good idea to choose a short name here if possible. 

In the edit panel, you can also choose to add status tags to the responsibility. This is something you do if you want users to pass item-related objects between them, for example when you want to have an acceptance status set to control who accepts and updates objects at a certain stage in their life-cycle (more about this in Restricting Access by Status).

Adding a Responsibilities to an Item and Occurrences

Responsibility is typically assigned to Items but when required additional alternative Responsibility values can be assigned to individual Occurrences of Items. 

This may be of use where a particular Occurrence of an Item passes from one Responsibility to another for a particular Instance.

In the example below the Water dispenser has 3 Occurrences in the Gymnasium but we want one of the Occurrences to be editable by a user with Hydraulic Engineer Responsibility. The Occurrence is selected and the Responsibility changed in the Occurrences Property Panel:

Open

In general, once the Responsibility Groups have been set up, you can add any Responsibility Group you have access to, to any Item you have edit access to.

In the figure below, the user has limited responsibility to EPLAN only. Therefore, the user can update (or create or delete) an Occurrence of an item with responsibility EPLAN, but cannot change the responsibility to ARC, for example.

Restricting user access

Restricting which users should have what responsibility, is done in the Web admin interface (see under "modify item rights for a user"). If what you want to do is to restrict the user to only create and update some objects - for example, only occurrences tagged with "EPLAN" - we advice giving the user 3-read as the overall access, and upgrad to 2 - Limited on the responsibility group EPLAN. This will give the user the ability to see other items on the room, for example, limiting the possibility of creating duplicates because one cannot see what is in the database.