1.3.5 Controlling view permissions for individual Items

Large-scale environments can consist of large numbers of systems, and the Items generated in these environments are often significant to more than one system. In this scenario, a system called a base system can be set up to be shared among the systems in the environment. When a base system is in place, a JP1/Service Support user (person in charge) can escalate incidents that relate to multiple systems to the base system for processing. Because access permissions in JP1/Service Support apply at the process work board level, all users with access permission for the base system are able to view Items that have been escalated to the base system. Inevitably, this includes users who have no direct involvement with the Item. By assigning view permissions for individual Items, you can prevent these escalated Items from being shown to users to whom they are irrelevant.

The following figure shows an operation example in which view permissions are set for individual Items:

Figure 1‒14: Example of setting view permissions for individual Items

In this example, the environment incorporates a received order management system, a placed order management system, a shipment management system, and a base system. The person in charge of each system (user A, user B, and user C) has view permission for the process work board of his or her own system, and that of the base system. When the option to set view permissions for individual Items is enabled, you can stop others from seeing Item A1 by assigning view permission for Item A1 to user A only. This makes user A an Item view permissions owner for Item A1.

For details on setting view permissions for individual Items, see 3.11 Item access control.

To Page Top