Restrict access to CI's that agents do not serve

Moderator: crythias

Locked
yuri0001
Znuny superhero
Posts: 630
Joined: 17 Mar 2011, 14:40
Znuny Version: 5.0.6
Real Name: Yuri Kolesnikov
Location: Russia

Restrict access to CI's that agents do not serve

Post by yuri0001 »

Good day everyone!
That is the question. I am afraid that the decision not normal, but can someone tackled and found a workaround?
Say there is a CMDB with configuration items of various classes and geographically distributed. They, of course, serve by the local groups, as a first level tech support. So they can watch and update information on their CI they should be in a group - itsm-configitem and have the rights -rw. But then they have access to all CI's. The group itsm-configitem have no links to the location of CI.

Question:
How do I restrict access to CI's, they do not serve? :?
Best regards Yuri Kolesnikov
OTRS 5.0.14, ITSM 5.0.14
SUSE 13.2, MariaDB 10.0.22(productive)
OTRS 5.0.14, ITSM 5.0.14(test)
Alexander Halle
Znuny expert
Posts: 296
Joined: 04 Jul 2010, 17:49
Znuny Version: 3.1.x
Real Name: Alexander Halle
Company: radprax MVZ GmbH
Location: Wuppertal
Contact:

Re: Restrict access to CI's that agents do not serve

Post by Alexander Halle »

Currently one can restrict CI classes to agent groups. This can be done by defining a group for the according class in the General Catalog --> ITSM::ConfigItem::Class .

I'f you need further possibilities please create a feature request at http://otrsteam.ideascale.com/ .
Alexander Halle System: OTRS 3.1.x, Ubuntu 10.04.x LTS, MySQL 5.1.x, Apache 2.2.x
OTRS Community Links: User Meetings, Projects
Locked