You are not logged in.

Announcement

 Téléchargez la dernière version stable de GLPI      -     Et vous, que pouvez vous faire pour le projet GLPI ? :  Contribuer
 Download last stable version of GLPI                      -     What can you do for GLPI ? :  Contribute

#1 2010-09-13 01:45:13

abdon
Member
Registered: 2010-08-23
Posts: 101

Groups vs. entities

I have been reading but I'm still having a hard time understanding groups vs. entities, and when you would use one or the other.  Could somebody please explain why the following is the way it is?


1. Users can be added to both groups and entities, but the ones added to an entity can be assigned a profile.
2. Groups can be moved under an entity.
3. Entities can be made hierarchical. Groups have something called child entities, but  I can't see how to make it work.
4. Inventory items can be added to groups but not to entities (but as mentioned groups can be moved under an entity).
5. Rules and documents can be assigned to entities but not to groups.

Your input would be most appreciated. Thanks in advance.

Offline

#2 2010-09-16 01:07:38

abdon
Member
Registered: 2010-08-23
Posts: 101

Re: Groups vs. entities

I still trying to get a clear idea on how to use groups and entities. I'm trying to avoid programming myself into a corner if it can be helped.

When should I use one vs. the other? Or both? Could somebody provide some examples?

Thanks, take care.

- Abdon

Offline

#3 2010-09-16 13:18:08

FranciX
Member
From: Málaga - Spain
Registered: 2009-07-01
Posts: 51
Website

Re: Groups vs. entities

I hope somebody could do this. I also have problems to know how to use each one.


Plugin genericassets
Go and use it!

Offline

#4 2010-09-16 15:36:41

sean.tapscott
Member
Registered: 2010-06-16
Posts: 303

Re: Groups vs. entities

To me, and this is just guessing, entities are more like buildings.  Entities tend to separate Technicians and computers from each other.  They can also have different business rules.  Typically, technicians local to an entity don't travel between entities.  Now, if you have a "root" technician, you put him higher in your entity hierarchy so they can see all the child entities and can see and act on tickets beneath them.

Groups are the organizational units inside the entities, or you could say buildings.  Sales and Support are two different groups, but probably don't require much separation besides being in different groups.  Engineering is in a different building though, and requires vastly different permissions for the users, and that can be easily separated by entities but not by Groups.  You might want your engineers to be able to see other people's tickets or maybe even have control over them like technicians would.  Computers don't tend to exist or travel between buildings (entities), and you have to physically and virtually "transfer" them if you do want to transfer them to a different building (entity). 

Also, separating the engineering group and building into a separate entity will allow you to have greater control over the business rules, and in the future, probably have greater control over plugins and their actions. 

Another useful thing about entities is that you could separate helpdesks using them.  Right now, I've been considering allowing the facilities maintenance guy access to the helpdesk so he can manage his servicing of equipment and organize himself better.  BUT, I wouldn't want him to be able to see what we're doing, and I probably don't want to see what he's doing.  I'd put him in a entity next to mine, and move mine down from the root entity.  It would look like a big Arch, with IT being on one end and Facilities Maintenance on the other.  I'd leave the users in the root entity, so we would both be able to tie issues to them, and send them followup on their reported issue. 

Again, this is all only guessing and extending the spirit of the entity feature that I've seen so far.  I'm sure there are some corrections to be made, and would hope the developers would take a little time to correct me.  Besides that, I'm sure in .78 things will change slightly so this is probably already obsolete.


Now using 0.78.1 on CentOS.

Offline

#5 2010-09-21 01:31:28

abdon
Member
Registered: 2010-08-23
Posts: 101

Re: Groups vs. entities

Outstanding. Thank you very much.

Offline

#6 2010-12-02 17:27:02

bunak
Member
From: Nizhyn, Ukraine
Registered: 2010-10-01
Posts: 53

Re: Groups vs. entities

Thank for full answer.

sean.tapscott wrote:

Groups are the organizational units inside the entities, or you could say buildings.

Is it possible to create subgroup inside group?
For Example create Finance Department as group and Buhgalter unit as sub group inside Finance Department?

Last edited by bunak (2010-12-02 17:27:28)

Offline

#7 2010-12-02 17:41:59

sean.tapscott
Member
Registered: 2010-06-16
Posts: 303

Re: Groups vs. entities

In Active Directory, yes, but in GLPI 0.78.1, it seems not.  What would you gain from having a subgroup?  There's probably another way to achieve the functionality.


Now using 0.78.1 on CentOS.

Offline

#8 2010-12-03 15:05:14

bunak
Member
From: Nizhyn, Ukraine
Registered: 2010-10-01
Posts: 53

Re: Groups vs. entities

sean.tapscott wrote:

What would you gain from having a subgroup?  There's probably another way to achieve the functionality.

I need to know what computer equipment is used in the Units of our organization. Units consist of offices and departments.
the first way that I tried do it - is by set Entites in computer equipment. But after reeding your post I try specify the units in groups. But they not have a tree.

Offline

#9 2010-12-03 16:08:20

sean.tapscott
Member
Registered: 2010-06-16
Posts: 303

Re: Groups vs. entities

Yeah, I think you'd have to do it with entities so that when you move the computers or devices between departments you can use the transfer function to simulate all the disconnecting of printers and such.


Now using 0.78.1 on CentOS.

Offline

Board footer

Powered by FluxBB