-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
modify preferences - Assets/computer #124
base: master
Are you sure you want to change the base?
Conversation
|
||
|
||
|
||
**-------------------OLD DOCUMENTATION-----------------** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The whole "old documentation" should certainly be removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, of course, but I don't want to delete anything until I'm sure that all the information has been transferred elsewhere.
:align: center | ||
:scale: 42 % | ||
|
||
you can define whether GLPI displays notifications when changes are made (updating a ticket, adding a task, etc.). you can define whether these should be displayed : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can define whether GLPI displays notifications when changes are made (updating a ticket, adding a task, etc.). you can define whether these should be displayed : | |
You can define whether GLPI displays notifications when changes are made (updating a ticket, adding a task, etc.). You can define whether these should be displayed: |
|
||
The alternate username is a field returned by the inventory. It is filled in by the user who opened the session on the machine concerned. | ||
This field can be updated if, during the next inventory, another user logs on to the machine.It takes the form ``user@machine_name``. This field can be changed manually, | ||
but it will be locked (by default) to prevent it being updated at a later date. See the article on :doc:`locks` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is no "lock" page
:align: center | ||
:scale: 51% | ||
|
||
- To create a group, click on **+ Add** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Group in charge creation is the same as group creation. We should only document what changes for "in charge".
|
||
Once the group has been created, you can add another or select it from the drop-down list. | ||
|
||
.. Note:: If you cant another option with groups, see :doc:`../administration/groups` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not understand the sentence
|
||
You can add location manually or dynamically. | ||
|
||
.. warning:: Depending on your needs, pay attention to the entity you are in and its recursivity, so that it is visible or not to other entities. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not only for locations. I guess this should be a more generic warning,
|
||
.. warning:: Depending on your needs, pay attention to the entity you are in and its recursivity, so that it is visible or not to other entities. | ||
|
||
.. Note:: All locations your created here are available for other GLPI objects depending on the entity in which you created it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess it can be removed
* Now, select the location for your computer | ||
|
||
|
||
To add a location **automatically** : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe I'm wrong, but inventory will create automatically locations even if there are no rules. Rules will more affect location.
To me, the "manually" and "automatically" differences is not correct here.
|
||
To add a location **automatically** : | ||
|
||
You need to create **location rules** to affect a location to a computer. Before, you need to define the criteria which will trigger the rule (a tag inventory, a subnet, a domain, etc.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe a better place would be with other rules in admin module (with a link to it here).
Manufacturer | ||
~~~~~~~~~~~~~ | ||
|
||
Manufacturers are automatically retrieved by the automatic inventory and assigned to the computer. you can also create/add them manually. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Manufacturers are automatically retrieved by the automatic inventory and assigned to the computer. you can also create/add them manually. | |
Manufacturers are automatically retrieved by the automatic inventory and assigned to the computer. You can also create/add them manually. | |
:scale: 63% | ||
|
||
|
||
Example with picture : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example with picture : | |
Example with picture: | |
|
||
If you insert a machine with photos in a rack, the photos will be visible in that rack | ||
|
||
Example of a server in a rack with photo : |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Example of a server in a rack with photo : | |
Example of a server in a rack with photo: | |
Serial number | ||
~~~~~~~~~~~~~ | ||
|
||
This information is automatically retrieved by the automatic inventory. You can add/modify this information manually. By default, if you add or modify this field |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Globally, all fields can be locked. I guess it would be better to have a lock § somewhere, rather than explain lock on each related field.
~~~~~~ | ||
|
||
The status provides information about the state of the machine. | ||
By default, there is no status. You can create as many statuses as you like, which can be used by rules. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if it's usefull. By default, GLPI provide no dropdown content (and if it does for few ones, maysbe it's better to just document those ones).
Notions | ||
~~~~~~~ | ||
|
||
2 concepts need to be understood: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2 concepts need to be understood: | |
Two concepts need to be understood: | |
Passwords must follow the defined security policy. A real-time check of the entered password is then carried out. | ||
|
||
See the :doc:`secruity <../modules/configuration/general/security>` tab in the configuration module |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See the :doc:`secruity <../modules/configuration/general/security>` tab in the configuration module | |
See the :doc:`security configuration tab <../modules/configuration/general/security>`. |
Co-authored-by: Johan Cwiklinski <[email protected]>
Maybe 'gitbook" stuff should be done in another PR |
No description provided.