feat(content): update administration>entity #152
Conversation
|
Need to modify the screenshot of documents tab and and edit the note tab |
|
|
||
| Using entities is very useful for a company where management is hierarchical and where employees must have access to the assets depending on the division they belong to. | ||
|
|
||
| One entities creating in GLPI, assets inventory, users, profiles and assistance service become dependent upon entities: a computer can be assigned to an entity, |
There was a problem hiding this comment.
I don't understand what is meant here.
There was a problem hiding this comment.
I'm not sure I understand what you don't understand. This part explains (or at least tries to) what an entity is and what it's used for. Is it the turn of phrase that is the problem?
There was a problem hiding this comment.
"One entities" -> Entities is the plural form, but it seems like only One is being referenced here.
"One entities creating" -> Creating what? It sounds like the entity is creating something.
Since I can't figure out how the beginning of the sentence is supposed to be worded, the rest of the sentence doesn't make sense to me.
There was a problem hiding this comment.
Oh, damn, yes, you're right, it's not clear at all. Is it clearer like that?
Once an entity is created in GLPI, it can group together the inventory of assets, users, groups, profiles, etc. All these elements then become dependent on this entity, just like the support service;a computer can be assigned to an entity, a ticket can be declared on an entity, profiles and authorizations can be specific to entities… Automatic entity assignment for users and assets are possible thanks to rules management
|
|
||
| A user can be attached to several entities with different authorizations in each entity, these authorizations being kept in daughter entities or not. For example a user will be able to open a ticket only inside user's division, the ticket applying only to the items of the same division. | ||
|
|
||
| On the contrary, a user being granted larger authorizations will be able to view all items, tickets and other objects, and this on all entities in which user's authorizations apply. |
There was a problem hiding this comment.
I don't understand what is meant here.
There was a problem hiding this comment.
Same here, can you explain to me what is not clear?
There was a problem hiding this comment.
"A user can be attached to several entities with different authorizations in each entity, these authorizations being kept in daughter entities or not." -> "A user can have different authorizations in different entities and these authorizations can be made recursive to apply optionally to child entities".
"For example a user will be able to open a ticket only inside user's division, the ticket applying only to the items of the same division." -> The first part I understand. Is the second part referring to only being able to associate assets and other items in the same entity as the ticket?
"On the contrary, a user being granted larger authorizations will be able to view all items" -> "Larger" doesn't seem like the right way to describe it, but I don't understand what is being described. Is this referring to having permissions on a parent entity or having more permissions?
There was a problem hiding this comment.
I've just modified the first part with your suggestion.
For the second part, it concerns GLPI elements in a global way (asset, FAQ, problem, category, etc.). The goal is to clearly specify that a user is limited to their own entity and that if they don't have the necessary permissions, they won't be able to view elements from other entities :
For example, a user can be attached to several entities with different permissions in each entity, these permissions being retained (or not) in child entities. Without permission, they will then only be able to view the elements from their own entity that they would like to link to this ticket (FAQ, asset, category, etc.).
Indeed, it's not clear. I suggest:
On the other hand, if a user has sufficient permissions (see profile, and I'll provide a link to that part of the documentation), they could then see certain items that are not allowed for other profiles. For example, a user with a technician profile could see their entity's inventory, while a manager could see the inventory of the parent entity and all child entities. We can also assume that an IT technician could only see the computers in their entity, while an infrastructure technician could see all the assets (network equipment, racks, enclosures, etc.) in that same entity.
Co-authored-by: Curtis Conard <[email protected]>
No description provided.