peppermint-data / data /glpi_knowledge_documents.json
miller345's picture
Add seeded environment data, provenance, statistics, and dataset card
c83190f verified
Raw History Blame Contribute Delete
446 kB
{ "version": "1.0", "generatedAt": "2026-07-22T19:06:23+00:00", "generatedFor": "Peppermint additive GLPI knowledge expansion", "totalDocuments": 100, "source": { "project": "glpi-project/doc", "repositoryUrl": "https://github.com/glpi-project/doc", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" }, "documents": [ { "id": "GLPI-DOC-0001", "title": "Defining actors and roles", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "actors" ], "relatedIssuePatterns": [ "assistance", "actors" ], "summary": "An assistance service usually defines the following roles:", "sections": [ { "title": "Overview", "items": [ "An assistance service usually defines the following roles:", "Requester : user or group of users known to GLPI and affected by the ticket;", "Technician: ticket processing is done by a technician, by a group or by a supplier;", "Watcher : user who can follow a ticket but without modifying it; follow-up can be done from GLPI interface or by receiving notifications.", "Visible information and possible actions are defined by GLPI based on the user's role, which is defined in user's profile:", "Technicians are the actors having the most complete information on a ticket and the widest possible actions", "Requester and watcher will only view the information needed to fulfill request.", "For multiple users or groups, only the first user or group is defined when creating the ticket, more actors are added later. A user who cannot modify actors but able to see the ticket can become a watcher.", "When associating a new actor to a ticket, the number of tickets assigned to this actor is visible; this eases for instance task partitioning between technicians.", "for users who are not known to GLPI, mail address can be associated to a ticket. Default choice for requester and watcher (no selected user) allows to add a mail address in these fields; for this to be available, notifications must be activated (see notification management )", "Role attribution is done in user's authorization management (see Attribute authorizations to a user )" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/actors.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/actors.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/actors.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0002", "title": "Categories", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "categories" ], "relatedIssuePatterns": [ "assistance", "categories" ], "summary": "by selecting a parent category using in first tab the field As child of", "sections": [ { "title": "Overview", "items": [ "A category can be made hierarchical:", "by selecting a parent category using in first tab the field As child of", "by adding a new child category in tab ITIL Categories" ] }, { "title": "ITIL categories", "items": [ "ITIL categories can be managed in dropdown setup Setup > Dropdowns > Ticket Categories.", "ITIL categories are used by Tickets, Changes and Problems.", "A person in charge and/or a technical group can be added to this category and will then be used for notifications.", "A knowledge base category can also be associated to this category; this will register the solution in this category of the knowledge base.", "In this example, if you have a ticket with the category \"Hard disk failure\" which is linked to the KB category \"Failure > Computer\", when you add a solution to the ticket with \"Save to Knowledge base\" set to \"Yes\", the default category in the new Knowledge base Article form that opens will be \"Failure > Computer\".", "A category can be invisible in simplified interface, in order to reduce list of categories for end-users. It can also be made visible or not for incidents, demands, problems or changes.", "A template can be associated with this category and will be loaded when this category is selected in ticket. This template can be different for demands and incidents.", "When building a helpdesk, it is important to choose carefully the list of available categories: a too large number visible by end-users will make ticket creation less easy, whereas a too small number will not allow you to correctly qualify the demand.", "Ticket categories allow to do automatic processing when creating a ticket, for instance modify ticket attributes; see Business rules for tickets ." ] }, { "title": "Task categories", "items": [ "Task categories are used to sort task in order to ease their processing or to build meaningful statistics." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/categories.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/categories.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/categories.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0003", "title": "Manage changes", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "changes" ], "relatedIssuePatterns": [ "assistance", "changes" ], "summary": "A change is a modification of the information system's infrastructure.", "sections": [ { "title": "Overview", "items": [ "A change is a modification of the information system's infrastructure.", "A change can be created either from a ticket form or a problem form, in tab Changes, or from menu Assistance > Changes.", "The form to create a change is similar to the ticket creation form and shares with it many terms: requester, watcher, assigned to, status, urgency, impact, priority, category. For more information see Manage tickets . The validation process is also the same as tickets in order to allow preliminary validation of the change (tab Validations).", "Once the change is created, it is possible to attach tickets but also impacted items (tab Items). An analysis phase (tab Analysis) consists in describing impacts and controls list in order to implement this change through a deployment plan, a backup plan and a checklist (tab Plans).", "Same as tickets, task, costs and solution allow to follow and solve the change. For complex changes management, a change can be linked with one or several projects allowing a mode detailed management (Manage projects ).", "Changes use their own notifications (see configuration of email follow-ups )." ] }, { "title": "Add a change", "items": [ "To add a new change, click on + Add at the top of the screen", "Fill in the various tabs of your change to make it as complete as possible" ] }, { "title": "Status", "items": [ "Several statuses are available, including some for test phases, validation, qualification, etc." ] }, { "title": "Delete a change", "items": [ "To delete a change, click on the change concerned", "Click on put in trashbin at the bottom of the screen" ] }, { "title": "Restore or delete permanently", "items": [ "To delete or restore a change, click on the trashbin (at top right of screen)", "Select the change concerned", "Click on Actions", "Select Restore or Delete permanently", "Click on Post" ] }, { "title": "Analysis", "items": [ "This tab contains :", "Impacts", "Control list in order to implement the change." ] }, { "title": "Plans", "items": [ "This plan contains :", "Deployment plan", "Backup plan", "Checklist" ] }, { "title": "Statistics", "items": [ "The statistics are intended to provide information, showing how long it takes to take over, close a change, etc. Statistics similar to tickets" ] }, { "title": "Approvals", "items": [ "Approval allows you to send requests to groups and/or users (or certain users within a group) in order to obtain their validation of the change in question. You can see Approvals for more information." ] }, { "title": "Problems", "items": [ "Changes may be due to problems. In this tab, you can link a problem to your change.", "Problems can be linked in several ways :", "Linked To", "Duplicates", "Son of", "Parent of", "Problems can be linked in several ways. This information is for information purposes only." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/changes.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/changes.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/changes.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0004", "title": "Life cycle matrix", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "lifecyclematrix" ], "relatedIssuePatterns": [ "assistance", "lifecyclematrix" ], "summary": "Each profile having its own life cycle matrix, it is possible to refine which profile will be able to do which action.", "sections": [ { "title": "Overview", "items": [ "Each profile having its own life cycle matrix, it is possible to refine which profile will be able to do which action.", "The life cycle matrix controls object status changes, which implies it can block some actions. If a status is not activated, it won't be present in the list of status of the object." ] }, { "title": "Ticket life cycle matrix", "items": [ "See Ticket management rules .", "In example above, a New ticket will never be put to Waiting, this status being not proposed in the ticket.", "Furthermore, a requester will not have access to solution validation form, because a solved ticket for which solution has been approved becomes closed, which is not authorized by the example.", "For the simplified interface, ticket life cycle allows to define if user can close a ticket (solution approved) and if user can re-open it event if it is closed." ] }, { "title": "Problem life cycle matrix", "items": [ "See Ticket management rules .", "In example above, a New problem will never be put directly to status Solved, this status being not proposed in the problem." ] }, { "title": "Change life cycle matrix", "items": [ "See Ticket management rules .", "In example above, a New change will never be Accepted before having its status put to Evaluation or Validation, this status being not proposed in the change." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/lifecyclematrix.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/lifecyclematrix.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/lifecyclematrix.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0005", "title": "Managing plannings", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "planning" ], "relatedIssuePatterns": [ "assistance", "planning" ], "summary": "Planning view allows to display planned tasks attached to a ticket, a problem or a change as well as planned notes or plugins' planned elements.", "sections": [ { "title": "Overview", "items": [ "Planning view allows to display planned tasks attached to a ticket, a problem or a change as well as planned notes or plugins' planned elements.", "This menu is only visible if profile includes View planning authorization.", "Date and time slot can be selected. A filtering on objects to include in planning is also available.", "Four views are available, depending upon user authorizations:", "Personal view : includes only the elements of the connected user;", "Group view: includes only the elements of the connected user's group, needs See planning of group's persons authorization;", "Users view: includes the planning of a particular user, needs See all plannings authorization;", "Groups: includes the planning of a particular group, needs See all plannings authorization;", "This information can be exported in two formats:", "Ical, in order to integrate planning in third-party tool calendar;", "Webcal, which allows to subscribe a third-party calendar to GLPI planning.", "Access to Ical and Webcal feed is protected by a security key integrated into the URL. It is possible to regenerate this key in menu Preferences. See Manage preferences .", "User's planning can be displayed on home page if profile has authorization See my personal planning. However, it is not possible to add an element to a planning from this interface; it is mandatory to plan a task or a note so that planning fills up." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/planning.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/planning.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/planning.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0006", "title": "Matrix of calculus for priority", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "prioritymatrix" ], "relatedIssuePatterns": [ "assistance", "prioritymatrix" ], "summary": "This matrix is common to all help desk items (tickets, problems and changes) and can be parameterized in tab Assistance of menu Setup > General.", "sections": [ { "title": "Overview", "items": [ "This matrix is common to all help desk items (tickets, problems and changes) and can be parameterized in tab Assistance of menu Setup > General.", "ITIL best practices separate urgency (as defined by the user) from incident impact (a user, a service, a functionality...) which is usually set by the technician. A matrix is then used to compute the priority associated to the item of the help desk (ticket, problem or change) as a function of both urgency and impact. GLPI provides a default predefined matrix which corresponds to standard cases.", "This predefined matrix can be modified in tab Assistance of menu Setup > General (see Configure general parameters .", "Knowing that the order of items processing by technicians is based on priority, it is possible to select the different levels of urgency, impact or priorities that will be used in the help desk and to disable some of them. This action allows to ease declaration of an incident and its processing. To disable a level, this level must be set to No. Medium level cannot be disabled.", "In example above, the urgency level Low will not be proposed to requester and the impact level High will not be proposed to the technician.", "The Major priority used by tickets is not part of the matrix. This level is higher than any other and requires the permission to modify priority in order to be able to assign it. A Major incident is a ticket whose processing is of such high importance that it overrides any other ticket." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/prioritymatrix.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/prioritymatrix.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/prioritymatrix.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0007", "title": "Manage problems", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "problems" ], "relatedIssuePatterns": [ "assistance", "problems" ], "summary": "A problem is the cause of potential incidents and, once identified, can be managed in GLPI.", "sections": [ { "title": "Overview", "items": [ "A problem is the cause of potential incidents and, once identified, can be managed in GLPI.", "Creating a problem object can be done either from the ticket form, in tab Problem, or directly from menu Assistance > Problems.", "The problem creation form is very similar to the ticket creation form and shares with it many concepts: Requester, Watcher, Assigned to, Status, Urgency, Impact, Priority, Category. For more information, see Manage tickets .", "Check what is means From tickets list, an alternative solution can be associated to linked tickets without solving the problem. Depuis la liste des tickets, une solution de contournement peut être associé massivement aux tickets liés sans pour autant résoudre le problème.", "Problems use their own notifications, see configuration of email follow-ups .", "Statistics similar to tickets are available for problems, see Display statistics ." ] }, { "title": "Analysis", "items": [ "This tab contains problem analysis.", "It consists of 3 inserts:", "Impacts", "Causes", "Symptoms" ] }, { "title": "Statistics", "items": [ "Statistics similar to tickets are available for problems." ] }, { "title": "Tickets", "items": [ "List all tickets are linked to the problem. You can add a new ticket or link an existing ticket" ] }, { "title": "Changes", "items": [ "This tab allows to display changes associated with the problem and add new changes. See changes" ] }, { "title": "Costs", "items": [ "The cost represents the financial impact of the problem encountered. It can be human, material or fixed." ] }, { "title": "Projects", "items": [ "You can attach or add one or more projects to your problem." ] }, { "title": "Tasks", "items": [ "A task is an action linked with a problem, usually a technical intervention. See Tasks" ] }, { "title": "Items", "items": [ "This tab allows to attach an item to the problem by choosing the type and the selected item. See Items" ] }, { "title": "Knowledge Base", "items": [ "You can link an article from the knowledge base . It is possible to add a new article by clicking on i" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/problems.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/problems.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/problems.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0008", "title": "Display statistics", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "statistics" ], "relatedIssuePatterns": [ "assistance", "statistics" ], "summary": "Statistics group reports on tickets as well as reports coming from plugins.", "sections": [ { "title": "Overview", "items": [ "Statistics group reports on tickets as well as reports coming from plugins.", "Reports can be parameterized on a given time slot." ] }, { "title": "Reports on tickets", "items": [ "Global:", "Display general statistics on tickets:", "Number of opened , solved, late and closed tickets;", "Average time of processing, resolution, closure and real duration;", "Number of satisfaction surveys, opened or answered;", "Average satisfaction.", "By ticket:", "Display statistics on tickets items, selected via a dropdown (requester, assigned technician, impact...).", "Table shows following items in four groups:", "Number of opened , solved, late and closed tickets;", "Number of opened satisfaction surveys, number of answers and average satisfaction;", "Average Take into account time (duration between ticket opening and first action on ticket, follow-up, task or solution), resolution time or closure time;", "Real ticket duration, average and total (real duration of allocated technician time for actions relevant for the ticket).", "By hardware characteristics:", "Displays statistics on computer items defined in associated items of a ticket (for example, model, operating system, motherboard...)", "The table groups the same numbers as defined in statistics by tickets.", "For these two types of reports, the button |stats_item| located on each result line allows to display the statistics as a graphic.", "By hardware:", "Display number of tickets assigned to each hardware, sorted by number of tickets.", "The option See graphics, when available, allows to display result as a pie chart.", "When statistics are done on a tree structured item (groups or categories for example), two presentations are available:", "Normal: all values are displayed", "Tree: only values at same level are displayed, taking into account the tickets attached to child elements. It is possible to navigate into values tree." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/statistics.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/statistics.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/statistics.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0009", "title": "Reccurent tickets", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "recurrentticket" ], "relatedIssuePatterns": [ "assistance", "recurrentticket" ], "summary": "Using templates, it is possible to program recurrent ticket opening.", "sections": [ { "title": "Overview", "items": [ "Using templates, it is possible to program recurrent ticket opening.", "Open a ticket every Monday to check that weekend backup was correctly executed", "Open a ticket first day of the month to perform initialization operations" ] }, { "title": "The different fields", "items": [ "Active: allows to disable temporarily ticket creation;", "Ticket template: model that will be used for ticket creation;", "Start date: start date for ticket creation, mandatory;", "End date: optional, defines ticket creation end date;", "Periodicity: ticket creation period;", "Preliminary creation: time for anticipated ticket creation;", "Calendar : allows to limit ticket creation days.", "Tickets will only be created if Active is Yes and if current date is between Start date and End date.", "Reccurent ticket opening is done through an automatic action named recurrent ticket, see Configure automatic actions ." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/recurrentticket.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/tickets/recurrentticket.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/recurrentticket.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0010", "title": "To go further", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "ticketadvanced" ], "relatedIssuePatterns": [ "assistance", "ticketadvanced" ], "summary": "Using ticket templates, it is possible to customize ticket creation form by masking, pre-defining or making mandatory some fields.", "sections": [ { "title": "Tickets categories", "items": [ "See Categories" ] }, { "title": "Tickets templates", "items": [ "Using ticket templates, it is possible to customize ticket creation form by masking, pre-defining or making mandatory some fields.", "See Ticket templates" ] }, { "title": "Collectors", "items": [ "External tools can interact with assistance module using mail collectors.", "Email is used to create tickets and add follow-up to existing tickets. A GLPI internal task will connect to a mailbox and fetch messages.", "The solution or closure of a ticket are not available via collectors.", "A mail message will go through the following steps:", "Mail box;", "Collector, configured using Configure collectors ;", "Rules, see Assigned a ticked opened by mail to an entity", "Business rules, see Business rules for tickets", "Ticket is created", "An answer to a mail coming from GLPI will go through the following steps:", "Mail box;", "Collector ;", "Creation of a follow-up for concerned ticket." ] }, { "title": "Recurrent tickets", "items": [ "See Recurrent tickets" ] }, { "title": "Attached costs", "items": [ "See Attached costs" ] }, { "title": "Links between tickets", "items": [ "It is possible to define links between tickets or to mark tickets as duplicates.", "See Links between tickets" ] }, { "title": "Processing time", "items": [ "Incidents resolution delays or SLA can be configured.", "See Configure SLAs ." ] }, { "title": "Business rules", "items": [ "Business rules can be defined to modify and assign tickets.", "See Business rules for tickets ." ] }, { "title": "Administrative closure", "items": [ "Administrative closure moves the status of a ticket from Solved to Closed.", "ITIL best practices recommends a validation of the solution by the ticket requester, who validates that the answer provided by the technician corresponds to the demand. However, if the requester does not fulfill this validation, it is possible to parameterize an administrative closure after a delay which can be configured at entity level (see Assistance tab ). If this delay is set to zero, the ticket is automatically closed." ] }, { "title": "Satisfaction", "items": [ "A satisfaction survey is triggered when the ticket status is set to Closed and the triggering delay is elapsed. This triggering delay is parameterized at entity level (see Delegate administration at entity level ).", "The automatic task that triggers the survey must be activated.", "When ticket is closed, a notification that includes a link to the satisfaction survey can be sent to the requester. The requester will also have access to the survey from the ticket form in tab Satisfaction.", "The requester can then select the satisfaction level (from 0 to 5, given as stars) about the ticket solution. A comment can also be added.", "Statistics on surveys are available in statistics .", "the requester can change the answer to the satisfaction survey within a delay of 12 hours after first answer", "a notification can be sent when satisfaction survey is generated, but also on each answer to this survey" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketadvanced.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/tickets/ticketadvanced.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketadvanced.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0011", "title": "Ticket life cycle", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "ticketlifecycle" ], "relatedIssuePatterns": [ "assistance", "ticketlifecycle" ], "summary": "Ticket life cycle is defined at profile level in a life cycle matrix . To display a life cycle and modify it, it is therefore done in profile management form (menu Administration > Profiles).", "sections": [ { "title": "Overview", "items": [ "Ticket life cycle is defined at profile level in a life cycle matrix . To display a life cycle and modify it, it is therefore done in profile management form (menu Administration > Profiles)." ] }, { "title": "Ticket types", "items": [ "GLPI tickets are either incidents or requests, this type being stored in field Type of the ticket. This type field allows to perform actions based on ticket type (see business rules for tickets modification and assignment , ticket templates and problem management ) and to customize the list of available categories." ] }, { "title": "Status", "items": [ "ITIL defines a standard for ticket status life cycle. This status life cycle is implemented in GLPI by defining the following status:", "New", "Processing (assigned)", "Processing (planned)", "Pending", "Solved", "Closed", "These status can neither be parameterized nor modified.", "It is therefore possible to hide some status according to profile (see Life cycle matrix ).", "To go further in status management, refer to ticket templates and business rules for tickets modification and assignment ." ] }, { "title": "Scheduling", "items": [ "Ticket scheduling is done according to data provided by the requester and the technician:", "Requester defines urgency", "Technician appreciates the impact", "Priority results from these two values. It is computed automatically using a matrix and provides the true importance of the ticket.", "To go further on this matrix configuration, see Define the matrix of calculus for priority ." ] }, { "title": "Management rules", "items": [ "The ticket status follows the following process:", "upon creation, the ticket has status New", "when a technician assigns ticket processing to a group, a technician or a supplier, the ticket goes to status Processing (assigned)", "when a new task is added to the ticket and is planned, ticket status become then Processing (planned)", "when a solution is found for the ticket, its status become Solved", "at last, then requester or writer validates the proposed solution, the ticket status is Closed", "Technician can change ticket status at every moment, in particular to put the ticket to Pending. Following ITIL recommendations, a ticket must be made Pending only by the requester, for example if request is not complete or if requester is not available for an intervention", "Requester can delete the ticket as long as the ticket status is New and no action has been done on the ticket" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketlifecycle.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/tickets/ticketlifecycle.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketlifecycle.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0012", "title": "Manage tickets", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "ticketmanagement" ], "relatedIssuePatterns": [ "assistance", "ticketmanagement" ], "summary": "GLPI assistance module is compliant with ITIL best practices guide for incident and request management: it integrates therefore notions such as impact, ticket urgency, priority calculus matrix and status standardization. Despite the fact that GLPI is ITIL compliant, it is not mandatory to follow these best practices and freedom is given to implement an incident management best tailored for organization's need.", "sections": [ { "title": "Manage tickets following ITIL recommendations", "items": [ "GLPI assistance module is compliant with ITIL best practices guide for incident and request management: it integrates therefore notions such as impact, ticket urgency, priority calculus matrix and status standardization. Despite the fact that GLPI is ITIL compliant, it is not mandatory to follow these best practices and freedom is given to implement an incident management best tailored for organization's need.", "Statistics are available for tickets, see Display statistics ." ] }, { "title": "Description of specific fields", "items": [ "Opening date: ticket creation date;", "Time to Resolve: date at which ticket must be solved;", "These two dates allow to limit in time incident or service request. A SLA can also be associated with the ticket; in this case the SLA and the next escalade level are displayed (see Configure SLA ).", "By: references the GLPI user having opened the ticket;", "Type: defines whether it is a request or an incident;", "Category: allows to sort request or incident by their nature, a category being associated to only one type;", "Status: status attributed manualy by the technician or dynamically by performed actions, see Management rules and life cycle matrix ;", "Request Source: indicates the channel used to create the ticket, see Configure drop down ;", "Urgency: importance given to the ticket by the requester;", "Impact: importance given by the technician;", "Priority: importance of the ticket automaticaly computed from defined impact and urgency using a predefined calculus matrix, see life cycle matrix ;", "Approval: by default the ticket is Not subject to approval;", "Items: list items associated to this ticket; field appearing only in ticket creation form, later editions will display items in a separate tab also used to associate new items to the ticket;", "Location: indicates the intervention location, has no link with the location of associated items nor with the requester location (for example roaming requester with a laptop);", "External ID: id for the ticket in an external system", "Actor: implied actors are referenced in the ticket, which allows them to be notified during ticket life cycle, see Defining actors and roles .", "If email followup have been configured (see notification management ), information about notifications are displayed for a user or a supplier: Email Followup (yes or no) and Email. Email is pre-filled with user's email if defined in user or supplier form. If no email is defined in user or supplier form, an email can be entered in text field.", "When using GLPI with multiple entities and having technicians with authorizations for several entities, it is not needed to switch current entity to declare a new incident inside an entity. Entity to which ticket will be assigned is determined as so: technician selects requester and GLPI find entities for which this requester has authorizations; if only one entity, ticket creation form is updated and ticket will be declared in this entity, if several entities, a drop-down list allows to select the entity to which ticket will be assigned.", "Title: if no title is defined by the user when creating the ticket, the first 70 characters of the description will be used to define ticket title;", "Description: mandatory, for above reason;", "Linked Tickets: defines a link between tickets, this link being of two types:", "Linked to: a simple link only used as information;", "Duplicates: when solving one of the duplicated tickets, the same solution is applied for other duplicated tickets which are therefore automatically solved.", "Missing description of Son of and Parent of" ] }, { "title": "Processing ticket", "items": [ "This tab displays exchanges between requester and personal in charge of the ticket; it allows to add information on the ticket such as requester call, ticket waiting for requester disponibility...", "This tab is the default tab when consulting a ticket except when the ticket is waiting for approval.", "To add a followup, click on Followup and enter a description.", "It is possible to choose the source of the followup, see Configure dropdown .", "A followup can be public or private. A private followup is only visible by GLPI users having the authorization See all followup and tasks. It allows for instance to have an exchange between technician which is not visible by requester.", "Adding, modifying and deleting a followup is submited to authorizations defined in profile, see Administer user profiles ." ] }, { "title": "Approvals", "items": [ "See Validation" ] }, { "title": "Project Tasks", "items": [ "A task is an action corresponding to a technical intervention related to the ticket.", "See Tasks" ] }, { "title": "Solution", "items": [ "This tab allows resolution of a ticket by a technican and approval of solution by requester.", "See Solutions" ] }, { "title": "Statistics", "items": [ "See Statistics" ] }, { "title": "Items", "items": [ "Allows to associate several items to the ticket.", "See Items" ] }, { "title": "Changes", "items": [ "Allows to add and display changes associated with the ticket.", "See Changes" ] }, { "title": "Problems", "items": [ "Allows to display and add problems associated with the ticket, or to create a problem from this ticket.", "See Problems" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketmanagement.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/tickets/ticketmanagement.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketmanagement.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0013", "title": "Opening a ticket", "category": "assistance", "tags": [ "glpi", "documentation", "assistance", "ticketopening" ], "relatedIssuePatterns": [ "assistance", "ticketopening" ], "summary": "A requester formulating a need can use several tools:", "sections": [ { "title": "Overview", "items": [ "A requester formulating a need can use several tools:", "filling an online form, the requester being known to GLPI or not;", "asking a delegate in the group to open the ticket (see Administer groups . In simplified interface, this is put into evidence by an option allowing to indicate if the ticket concerns the requesting user or another user. In standard interface, this mechanism is active as long as authorization See all tickets is set to No in the profile; all users for which delegation is active will be added as requester;", "contacting an operator directly or by phone, the operator will open the ticket;", "sending the demand by mail." ] }, { "title": "Opening a ticket in GLPI", "items": [ "A ticket can be opened:", "through the anonymous ticket opening interface, this interface being accessible by all non-authenticated users if GLPI general configuration allows it;", "through the graphical interface:", "simplified interface: lightweight form for an authenticated end-user;", "standard interface: full-fledged form." ] }, { "title": "Anonymous ticket opening interface for non-authenticated users", "items": [ "This interface can be accessed at URL http:///front/helpdesk.html; it allows users having no GLPI account to send an incident signaling form to the help desk. Once filled and submitted, a mail will confirm the ticket opening.", "The form can be customized by modifying directly file helpdesk.html.", "By default, ticket is created in root entity." ] }, { "title": "Opening a ticket in graphical interface", "items": [ "If templates are used (see Using templates ), some fields can be made mandatory, predefined or masked when opening the ticket (content, title and/or category). If a mandatory field is missing, the ticket will not be opened.", "The different fields are described in Manage tickets .", "It is possible to attach to the ticket one or more documents in one operation.", "When activating option Use rich text for assistance in general configuration, the Description field of the ticket will be able to be formatted as HTML. Moreover, an added zone will be available for images drag and drop, for example screenshots. A tag will then be added automatically to the description in order to formalize the content of the demand." ] }, { "title": "Simplified interface", "items": [ "This interface allows an authenticated user to open quickly a ticket, for the user or by delegation for another person.", "Ticket opening form can be accompanied by a message inviting user to check personal information (location, phone number) in order to be easily contacted by technicians.", "Specific fields:", "Inform me about he actions take:", "Appears if email followup are configured, see notification management . If set to Yes, the requester will be kept informed by mail of the different processing of the ticket. The field Mail contains the email address to which notifications will be sent. If several email addresses are defined, GLPI will select the default email defined in user's preferences. It is possible to select another email address or to enter an address if user's profile does not mention an email;", "Associated elements:", "Allows to associate an item of the inventory with the ticket. The content of the list depends upon parameters defined in user's profile (see Administer user profile .", "Watchers:", "Allows to add a watcher and to define notification parameters.", "Users can add new email addresses to the profile, see Manager preferences .", "If images or documents are added to the ticket, it is important to add them after having filled all mandatory fields marked with a red star, this because the reloading of the ticket opening form triggered by a missing mandatory field suppress attached images or documents.", "A message confirms the creation of the ticket which is then accessible by clicking on the ticket number highlighted in green." ] }, { "title": "Standard interface", "items": [ "To create a ticket, go to menu Assistance > Ticket then click add button with the \"+\" icon.", "When adding a new image from tab Documents of the ticket, the generated tag can also be used to insert image in ticket's description.", "A message confirms the creation of the ticket which is then accessible by clicking on the ticket number highlighted in green.", "A validation demand can also be done at ticket opening by indicating the desired validating user.", "When filling assigned requester, technician or group, information is displayed about the number of tickets this person or this group has opened or is in charge of. Similarly, when selecting an item, a simplified view of current tickets for this item is displayed." ] }, { "title": "Open a ticket by mail", "items": [ "Opening a ticket by mail is done by sending a mail to an email address defined in the collector (see Configure collectors", "On reception of the mail, a ticket will be opened automatically:", "message object will become ticket title", "body will become ticket description", "Cc: will become observers if emails are known to GLPI", "attachments will become attached documents of the ticket", "When activating option Use rich text for assistance in general configuration, the images present in the message body will become visible in the description of the ticket." ] }, { "title": "Open a ticket automatically", "items": [ "This mechanism is activated through Recurrent tickets ." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketopening.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assistance/tickets/ticketopening.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/tickets/ticketopening.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0014", "title": "Dictionaries", "category": "administration", "tags": [ "glpi", "documentation", "administration", "dictionnaries" ], "relatedIssuePatterns": [ "administration", "dictionnaries" ], "summary": "Dictionary's allow to modify data already existing in GLPI or new data in order to group redundant data.", "sections": [ { "title": "Overview", "items": [ "Dictionary's allow to modify data already existing in GLPI or new data in order to group redundant data.", "Dictionaries are based on GLPI rules engine and are available for some types of items (software, suppliers, drop-downs). The rules associated with a dictionary will modify values that are either manually inserted or automatically inserted via an inventory tool or via plugins (for instance CSV file injector)." ] }, { "title": "Import, export and duplication", "items": [ "Export, import and duplication are available for dictionarys or rules. These operations can be realized globally from dictionary's main page or by batch using mass actions from dictionary's search results. These functionalities are useful for instance when migrating rules from a pre-production environment to a production one." ] }, { "title": "Configure data dictionaries", "items": [ "A dictionary works the following way:", "data to be added enters the dictionary;", "rules engine plays all rules applying to this type of data and stops on first matching rule;", "modified data is returned by the dictionary and inserted into database.", "The Replay the dictionary rules button (under the list of rules of the dictionary) allows to replay the rules on data already existing in database.", "it is highly recommended to play rules on a test database and to backup database before production launch of the dictionary or before inserting new rules", "a script is available in directory scripts of GLPI installation, named compute\\_dictionnary.php, that allows to launch dictionary processing in command line mode; this allows to bypass problems of execution limit and provides a significant speedup" ] }, { "title": "Global dictionaries", "items": [ "Software ++++++++", "The software dictionary modifies software data (name, version, manufacturer) in order to complete or merge software's. It is used to make more coherent equivalent software for which name is not identical (for example Mozilla Firefox 3.0 and Mozilla Firefox 3.6) or to add a manufacturer if it is not present.", "This dictionary allows also to redirect the creation of a software or of a set of software in a given entity, by choosing action Entity and to select the entity in which to create the software. This functionality can also be used with general option Entity for software available in entity configuration.", "As an example, following image describes grouping Mozilla software. Criteria are accumulated with AND.", "Criteria for grouping Mozilla software", "The following image describes associated action for grouping Mozilla software.", "Action for grouping Mozilla software", "The following image presents result of grouping Mozilla software: software are grouped by type (Mozilla Thunderbird, Mozilla Firefox...) and versions are grouped by type.", "Result of grouping Mozilla software", "Autre exemple pour regrouper les mises à jour Windows. Cette fois le critères sont des OU et non des ET Critères Logiciel expression rationnelle vérifie /Correctif.\\XP.\\KB([0-9]\\)/ Logicel expression rationnelle vérifie /Mise.\\XP.\\KB([0-9]\\)/ Logiciel expression rationnelle vérifie /Update.\\XP.\\KB([0-9]\\)/ Actions Logiciel assigner Mise à jour Windows Version assigner valeur depuis regex #0", "Manufacturer ++++++++++++", "This dictionary allows to group under a unique name the manufacturer names coming from an inventory tool under different forms.", "regrouper les fabricants . Sun\\_Microsystems . Sun Microsystems, Inc. for the OpenOffice.org-Community . Sun Microsystems, Inc. . Sun Microsystems, Inc sous le nom Sun Microsystems.", "Printers ++++++++", "This dictionary allows to modify printer information based on manufacturer and/or name. It is possible to reject an import (for example printer name starting with //), to group printers under same name, to assign a manufacturer or to force management type (global or unitary)." ] }, { "title": "Drop-downs", "items": [ "This dictionary allows to modify drop-downs related to inventory: types and models of items, operating system, version and service pack.", "Models ++++++", "Possible criteria are manufacturer and item model.", "Often inventory tools extract model technical number, which is irrelevant for user. This example allows to extract commercial model name while keeping technical number which can be required in case of requesting a provider intervention.", "Example of dictionary for computer model: rule", "Example of dictionary for computer model: action", "The obtained result will be for instance: Netvista S42 (8319LGV)", "Types +++++", "Only possible criteria is item type.", "Example of dictionary on peripheral type: rule", "Example of dictionary on peripheral type: action", "The obtained result will be for instance: Keyboard", "Operating systems +++++++++++++++++", "Depending on chosen dictionary, the criteria will be based on operating system itself, on operating system service pack or on operating system version." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/dictionnaries.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/dictionnaries.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/dictionnaries.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0015", "title": "Entities", "category": "administration", "tags": [ "glpi", "documentation", "administration", "entities" ], "relatedIssuePatterns": [ "administration", "entities" ], "summary": "Entities are a key concept in GLPI. Having many similarities with a hierarchy or a division inside a company, it allows on a single instance of GLPI to isolate sets organized in a hierarchical manner. The chosen term is voluntarily neutral in order to adapt to many information systems.", "sections": [ { "title": "Overview", "items": [ "Entities are a key concept in GLPI. Having many similarities with a hierarchy or a division inside a company, it allows on a single instance of GLPI to isolate sets organized in a hierarchical manner. The chosen term is voluntarily neutral in order to adapt to many information systems.", "A single instance (or installation) of GLPI, when composed of several entities, allows to consolidate common data and rules. Using entities allows to create a tight isolation between organizational units.", "Segmenting in entities can have several targets:", "isolate assets of each division in order to limit assets visibility for groups or users", "isolate assets of clients", "reproduce the existing hierarchy of the directory (LDAP, Active Directory...).", "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.", "Once an entity is created in GLPI, assets inventory, users, profiles and assistance service become dependent upon entities: 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 .", "Root entity has two subsidiaries (Entity 1 and Entity 2) which in turn have two divisions each (Child-entity 1 et 2). Each entity has access to its assets and subsidiary entities:", "Root entity has access to its assets as well as to all assets of all entities", "Entity 1 has access to its assets as well as to child-entity 1 and 2 assets", "Child-entity 1 has only access to its own assets", "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 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.).", "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.", "By default, GLPI has a single generic entity named Root Entity. This entity can be renamed at user's convenience.", "Processes may vary depending upon entity; for this reason entities can have a delegate administration (authorization Entities in profile). This delegation must be granted to a very limited number of users who will be in charge of the complete management of the entity.", "When using GLPI in multi-entities mode, management of some configuration parameters can apply in a different way in each entity." ] }, { "title": "Entities", "items": [ "This tab lists existing sub-entities and allows to add a sub-entity to current entity." ] }, { "title": "Address", "items": [ "This tab groups administrative information of current entity:", "Phone", "Administrative number", "Fax", "Website", "Email", "Postal code", "Address", "City", "State", "Country", "Location on map", "Longitude", "Latitude", "Altitude" ] }, { "title": "Advanced information", "items": [ "This tab groups technical identification data of the entity, those concerning generic entity assignment rules and those concerning users search interface. This data will be used by rules for automatic assignment to the entity (hardware if coupled with an inventory tool, user or group if connected to a LDAP directory, ticket if enabled ticket creation via mail collector) as well as for import and synchronization of users originating from a LDAP directory." ] }, { "title": "Values for the genric rules for assignment to entites", "items": [ "Three options are available for generic entity assignment rules:", "Information in inventory tool (TAG) representing the entity: coming from inventory tool", "LDAP directory information attribute representing the entity: for example the DN of the entity", "Mail domain surrogates entity: the email domain associated with the entity" ] }, { "title": "Values used in the interface to search users from a LDAP directory", "items": [ "In order to offer to an entity administrator the possibility to import users from a LDAP directory,", "LDAP directory: directory associated with the entity", "LDAP filter associated to the entity (if necessary): associated with the entity search filter", "This search filter is meaningful only if entity definition is done by adding a restriction on LDAP filter. It is also possible to define the email domain specific to the entity which can be used to assign users to this entity." ] }, { "title": "Notifications", "items": [ "Notification setting is done at entity level." ] }, { "title": "Notification options", "items": [ "Administrator email address", "Administrator name", "Email sender email address", "Email sender name", "No-reply address", "No-reply name", "Reply-to address", "Reply-to name", "Prefix for notifications", "Delay to send email notifications (inheritance of the parent entity or delay in minutes)", "Enable notifications by default (No/Yes/Inheritance of the parent entity)", "Email signature", "URL of the application", "to send only one notification email. The email followup of an actor can also be defined to Yes or No." ] }, { "title": "Alarms options", "items": [ "Each entity will then by default get the values defined at parent entity level." ] }, { "title": "Cartridges", "items": [ "Reminders frequency for alarms on consumables: Inheritance of the parent entity/Never/Each day/Each week/Each month", "Default threshold for cartridges count: Inheritance of the parent entity/never/from 0 to 100" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/entity/entities.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/entity/entities.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/entity/entities.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0016", "title": "Forms", "category": "administration", "tags": [ "glpi", "documentation", "administration", "forms" ], "relatedIssuePatterns": [ "administration", "forms" ], "summary": "Since GLPI 11, forms are native, so the formcreator plugin is no longer required. Forms must be migrated from formcreator to forms.", "sections": [ { "title": "Overview", "items": [ "Since GLPI 11, forms are native, so the formcreator plugin is no longer required. Forms must be migrated from formcreator to forms." ] }, { "title": "Migration formcreator to forms", "items": [ "When migrating your instance to GLPI 11, the formcreator plugin must be installed. Once the migration is complete, enter the command in CLI mode from your GLPI folder:", "`php bin/console migration:formcreator_plugin_to_core`" ] }, { "title": "Forms by default", "items": [ "There are two pre-created forms by default:", "Report an issue", "Request a service", "These 2 forms are accessible to everyone. They can be deactivated/deleted/modified" ] }, { "title": "List of forms", "items": [ "The list of forms is available from Administration > Forms. They will also be visible from Assistance > Service catalog. This tab refers to the self-service profile home page (see Service catalog)." ] }, { "title": "Forms options", "items": [ "When creating a form (by + Add), several options will be available to customize and facilitate the user experience as much as possible." ] }, { "title": "Customize the formatting", "items": [ "Tools are available to customize the organization of the forms", "#. Add a new question #. Add a comment #. Add a new section #. Add an horizontal layout", "You can move the questions to reorganize the form", "There are tools to reorganize an entire section" ] }, { "title": "Basic information", "items": [ "Modify the form's title in the Underlined form file (this title will be visible to people with access to the form)", "Add a description to simplify the use of the form (this description will be visible to people with access to the form)" ] }, { "title": "Add questions", "items": [ "Each question has its own title field (identified by new question) and will be visible to the user. Each question can be made mandatory so that the user must fill in the field to validate the form", "There are actually several possible question types:", "Short answer: Text field with limited length and no formatting (bold, italics, color, etc.).", "This field has additional options:", "Text: Allows you to enter text (alphanumeric)", "Emails: Allows you to enter email addresses only", "Number: Allows you to enter numeric characters only", "Long answer: field limited to 65,535 characters. The formatting of this field can be customized by the user (bold, italic, color, etc.)", "Date and time: a date and/or time", "This field has additional options:", "Current date/time: Use the current date and/or time and not allow the user to change it (leave the box unchecked to allow the user to specify the date/time they want).", "Date: Specify the date only (without the time).", "Time: Specify the time of day.", "Actors: add one or more users/groups/suppliers referenced in GLPI", "This field has additional options:", "Requesters / Observers / Assignees: each users / groups / suppliers that will be added will be pre-filled in the ticket according to the type of actor that will be chosen.", "A user/group/provider can be preselected that the user can modify or not", "Allow multiple actors: allow multiple selections (allows groups, users and suppliers in the same field)", "Urgency: add an urgency (very low, low, medium, high, very high)", "Request type: select the type of request (incident or request)", "Document: add a document", "Radio: set up a response list. The user will only be able to select one response.", "An additional description can be added to make it easier for the user to choose.", "Checkbox: set up a response list. The user will be able to select multiple answers.", "An additional description can be added to make it easier for the user to choose.", "Dropdown: set up a drop-down list to select one or more answers", "This field has an additional option:", "Allow muliple options", "Item: Allows you to select differents GLPI's objects", "This field has additional options", "Users devices: allows the user to select their own assets", "GLPI Objects available :", "Computers", "Monitors", "Network devices", "Peripherals", "Phones", "Printers", "Licenses", "Certificates", "Unmanaged assets", "Custom Assets", "Software", "Cartridge models", "Consumable models", "Phone lines", "Passive devices", "PDUs", "Racks", "Tickets", "Changes", "Problems", "Recurrent tickets", "Budgets", "Suppliers", "Contacts", "Contracts", "Documents", "Projects", "Certificates", "Appliances", "Databases", "Clusters", "Data centers", "Reminders", "RSS Feed", "Users", "Groups", "Entities", "Profiles", "Dropdowns available:", "Locations", "Statuses of items", "Manufacturers", "Blacklists", "Blacklisted mail content", "Default filters", "ITIL category", "Task categories", "Task templates", "Solution types", "Solutions templates", "Approval templates", "Request sources", "Followup templates", "Project states", "Project types", "Project tasks types", "Project tasks templates", "External events templates", "Event categories", "Pending reason", "Service catalog categories", "Approval steps", "Computer types", "Networking types", "Printer types", "Monitor types", "Devices types", "Phone types", "License types", "Cartrige types", "Consumable types", "Contract types", "Contact types", "Generic types", "Sensor types", "Memory types", "Third party types", "Interface types (Hard drive...)", "Cases types", "Phone power supply types", "Files systems", "Certificate types", "Budget types", "Simacard types", "Line types", "Rack types", "PDU types", "Passive device types", "Cluster types", "Database instance type", "Custom Asset types", "Computer models", "Networking equipment models", "Printer models", "Monitor models", "Peripheral models", "Phone models", "Device camera models", "Device case models", "Device control models", "Device drive models", "Device generic models", "Device graphic card models", "Device hard drive models", "Device memory models", "System board models", "Network card models", "Other component models", "Device power supply models", "Device processor models", "Device sound card models", "Device sensor models", "Rack models", "Enclosure models", "PDU models", "Passive device models", "Custom Asset models", "Virtualization systems", "Virtualization models", "States of the virtual machine", "Document heading", "Document types", "Business criticies", "Databse instance categories", "Knowledge base categories", "Calendars", "Close times", "Operating systems", "Versions of the operating systems", "Service packs", "Operating systems architectures", "Editions", "Kernels", "Kernels versions", "Update sources", "Networking interfaces", "Networks", "Network port types", "VLANs", "Line operators", "Domain types", "Domain relations", "Records types", "Fiber types", "Cables types", "Cable strands", "Socket models", "IP networks", "Internet domains", "Wifi networks", "Networks names", "Software categories", "Users titles", "User categories", "LDAP criteria", "Ignored values for the unicity", "Fields storage of the login in the HTTP request", "Plugs", "Appliance types", "Appliance environments", "Resolutions", "Image formats", "USB vendors", "PCI vendors", "Webhook categories", "Custom dropdowns" ] }, { "title": "Configure visibility", "items": [ "Visibility conditions can be specified for a question based on the answer to a previous question.", "For example, a user reports an issue with a printer. Depending on the location (question type Item > Dropdowns > Common - Locations), the form could be conditional on displaying only a list of printers linked to that location.", "You can indicate whether the question should be shown or hidden based on chosen criteria.", "The available condition types:", "Always visible", "Visible if...", "Hidden if...", "Select the question from the drop-down list", "Select the condition:", "Is visible", "Is not visible", "Is equal to", "Is not equal to", "Contains", "Do not contains", "Match regular expression", "Do not match regular expression", "Is empty", "Is not empty", "Length is greater than", "Length is greater than or equal to", "Length is less than", "Length is less than or equal to", "Is greater than", "Is greater than or equal to", "Is less than", "Is less than or equal to", "Is of itemtype", "Is not of itemtype", "At least one of itemtype", "All items of itemtype", "Enter the desired value as needed." ] }, { "title": "Conditionnal Approval", "items": [ "It is possible to set conditional Approval (only on short/longer answer fields) using a Regular expression. This forces the user to enter a conditional answer, such as a certain number of digits, a maximum of 30 characters, etc.", "In this example, the expected response is a sequence of 6 numbers", "If the entered answer is not suitable, a red error message will appear during Approval." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/forms/forms.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/forms/forms.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/forms/forms.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0017", "title": "Groups", "category": "administration", "tags": [ "glpi", "documentation", "administration", "groups" ], "relatedIssuePatterns": [ "administration", "groups" ], "summary": "Groups tab allows to add, modify, delete, search groups.", "sections": [ { "title": "Overview", "items": [ "Groups tab allows to add, modify, delete, search groups.", "Groups can be defined in a hierarchical structure in order to ease navigation and search.", "Management > Division > Service` or `N3 Support > Network > LAN", "Groups can be used in several way to group users by:", "Skills: for the helpdesk, for example network technicians, or database administrators,", "Organizational groups: for example all the computers of the management or the accounting department but also set of persons to be notified.", "The options available to adjust these behaviors are:", "Visible in a ticket: requesting group and/or assignment to this group;", "Can be notified: recipient of notifications;", "Can be manager: only for a project ;", "Can contain: assets and/or users.", "In an item form, 2 notions of groups are available:", "Technical group which indicates which group of people is in charge of the asset (equivalent for a group of the technical manager)", "Group which indicates to which group of items it belongs.", "Likewise, it can be used in Business rules for tickets .", "A group can have one or more managers, concept which can then be used for notifications, for example to send an email to the manager(s) of the group when a ticket is opened, see notification management .", "The concepts of manager can be configured in the \"Users\" tab.", "Assigning a user o a group is either static and done using the GLPI interface, or dynamic when this is automatically extracted from the LDAP directory.", "A group is attached to the entity in which it is created and can then be visible in sub-entities.", "From the list of groups, a group can be imported from a LDAP directory via the LDAP directory link button if external authentication is used and the \"Auth and sync update\" authorization is granted in profile. The assignment of users to groups will be automatic, see Profiles . If several directories are configured, the choice between directories is proposed, otherwise the search form is directly accessible.", "Depending on how you search for groups (see Authenticating users from LDAP directories ), a Search filter in groups and/or a User search filter appear. These allow to refine the list to be imported. If multiple entities exist in GLPI, it is necessary to select the destination entity of the group as well as its visibility in the sub-entities.", "The only way to refresh from a directory the list of group members is to resynchronize users, see Import users from an external source ." ] }, { "title": "Import groups", "items": [ "In `Administration` > `Groups` > `LDAP directory link` (at the top of the page), you have the option to import groups. Depending on the settings made, users will be managed dynamically.", "For more information go to setup LDAP" ] }, { "title": "Child groups", "items": [ "This tab allows to add a subgroup to the selected group and lists the existing subgroups. Each subgroup created will also be visible in `Administration` > `Groups`" ] }, { "title": "LDAP directory link", "items": [ "This tab only appears if the \"Auth and sync update\" authorization is granted in profile; it gathers the information allowing GLPI to find the group and its users in the LDAP directory." ] }, { "title": "Security", "items": [ "In this tab you can force or not the use of 2FA for a specific group" ] }, { "title": "Users", "items": [ "This tab allows to add a user to this group by defining whether the added user is manager of the group. It also lists the users of this group with possible search by this criteria and also in the subgroups of the current group." ] }, { "title": "Notifications", "items": [ "List of notifications for which destination is group or group supervisor" ] }, { "title": "Created tickets", "items": [ "List all tickets created or assigned to the group. If a ticket is created by a group member, but the requester is not explicitly the group, the tickets will not be visible here. `Show all allows you to show all tickets created or assigned, you will then be redirected to Assistance` > `Tickets`" ] }, { "title": "Problems", "items": [ "List all problems created by the group. `Show all allows you to show all problems created by the group, you will then be redirected to Assistance` > `Problems`" ] }, { "title": "Changes", "items": [ "List all changes created or assigned to the group. `Show all allows you to show all changes created by the group, you will then be redirected to Assistance` > `Changes`" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/groups.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/groups.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/groups.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0018", "title": "Logs", "category": "administration", "tags": [ "glpi", "documentation", "administration", "logs" ], "relatedIssuePatterns": [ "administration", "logs" ], "summary": "This menu allows to display and sort logs.", "sections": [ { "title": "Overview", "items": [ "This menu allows to display and sort logs.", "The logs page displays type of modified information (computer, reservation, ticket...), the modification date, GLPI service (inventory, configuration, tickets...) and a message detailing the event.", "Log level can be parameterized in field Log Level of tab System of general configuration.", "Log retention period can be parameterized in automatic actions." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/logs.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/logs.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/logs.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0019", "title": "Mailing queue", "category": "administration", "tags": [ "glpi", "documentation", "administration", "mailqueue" ], "relatedIssuePatterns": [ "administration", "mailqueue" ], "summary": "All notification emails go through a queue before actual delivery. This allows keeping a history and a list of the various emails sent.", "sections": [ { "title": "Overview", "items": [ "All notification emails go through a queue before actual delivery. This allows keeping a history and a list of the various emails sent.", "An automatic action (`queuedmail) allows the sending of pending emails (see Configure automatic actions ). Another automatic action (queuemailclean`) cleans the queue by keeping only recent emails.", "The delay applied for sending notifications can be defined at entity level, see administration by entity ). This allows for example in the case of rapid multiple modifications of an object to send only one notification.", "Example of queue", "In the example above, the deadline for sending email notifications has been set to 20 minutes in the configuration of the entity; as a consequence the sending date is set at 20 minutes after the creation date.", "Once the notification has been sent, the queue is placed in the recycle bin with the date sent." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/mailqueue.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/mailqueue.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/mailqueue.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0020", "title": "Administration permissions", "category": "administration", "tags": [ "glpi", "documentation", "administration", "administrationtab" ], "relatedIssuePatterns": [ "administration", "administrationtab" ], "summary": "The 7 standard permissions will not be listed (see Permissions description ).", "sections": [ { "title": "Overview", "items": [ "The 7 standard permissions will not be listed (see Permissions description ).", "Some permissions apply globally to GLPI, other permissions may be delegated locally. This is indicated by the color of permissions zones, as described in image below.", "For example, profiles are defined for all entities; on the other hand, business rules may vary from one entity to another.", "Permissions zones" ] }, { "title": "User permissions", "items": [ "User permissions", "Read Auth: adds a field in the user form indicating the authentication method as well as the date of the last synchronization", "Update auth & sync:", "Displays a Synchronization tab in the user allowing to change authentication method and force synchronization;", "Adds a LDAP directory link button before the group list;", "Displays a LDAP directory link tab in the group containing the information allowing GLPI to find the group and its users in the LDAP directory.", "Add External:", "Allows the import or synchronization of a user", "Adds a ...From an external source button before the list of users" ] }, { "title": "Entity permissions", "items": [ "Update Parameters: allows to modify the data of the Assistance tab in the entity.", "Read Parameters: allows to view the data in the Assistance tab in the entity." ] }, { "title": "Business rules for tickets (entity) permissions", "items": [ "Rules permissions", "Parent Business: displays a applied rules (entity name) tab in the business rules for tickets. This tab lists all the played rules of the parent entities.", "The elements of the Dictionaries part fall within the 7 standard permissions.", "Dictionaries permissions" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/administrationtab.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/profiles/administrationtab.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/administrationtab.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0021", "title": "Assistance permissions", "category": "administration", "tags": [ "glpi", "documentation", "administration", "assistancetab" ], "relatedIssuePatterns": [ "administration", "assistancetab" ], "summary": "See My Ticket: see all the tickets for which I am the writer, the requester or the observer as well as their public follow-ups", "sections": [ { "title": "Simplified interface", "items": [ "Tickets permissions +++++++++++++++++++", "See My Ticket: see all the tickets for which I am the writer, the requester or the observer as well as their public follow-ups", "Create: adds a Create Ticket menu. If you do not have this permission, when you log in, you will be directed to the list of tickets. Otherwise, you will be redirected to the home page which displays my tickets, sorted by status, with the Create ticket menu as the table title.", "See Group Ticket: see the tickets created which have one of my groups as an requester or observer. For example, if I am a member of the Management group, I will see all the tickets having a requester in group Management.", "Followup permissions ++++++++++++++++++++", "See Public Ones: see all followups typed as public followups.", "Update followups (author): modify the follow-ups you have created.", "Add followup (requester): add a follow-up to a ticket for which I am a writer or requester. This right also allows you to add a document to a ticket.", "Add followup (associated groups): add a follow-up to a ticket for which the requesting group is one of the groups of which I am a member.", "Tasks permissions +++++++++++++++++", "See Public Ones: see all the tasks typed as a public task. This right also allows the display of the Tasks tab of a ticket.", "Validations permissions +++++++++++++++++++++++", "Validations permissions", "Validate an Incident: respond to a validation request concerning an Incident type ticket. Having this right makes you appear in the list of people who can validate.", "Validate a Request: respond to a validation request concerning a Request type ticket. Having this right makes you appear in the list of people who can validate.", "Create for Request: send a validation request for a Request type ticket.", "Create for Incident: send a validation request for an Incident type ticket.", "The Validation tab will only appear in the ticket if you have one of the validation creation permission. Otherwise, it will only be displayed if you have one of the validation permissions and only if the type of the ticket corresponds to the permission.", "Associations permissions ++++++++++++++++++++++++", "Associations permissions", "Link with items for the creation of tickets:", "My Devices: assets whose type is authorized and for which I am the user;", "All Items: all assets of my entity whose type is authorized", "Associable items to a ticket: types of asset on which a ticket can be associated. To add a type, just click in the white area and choose the authorized type or All if you want to authorize all types. To delete a type, simply click on the cross to the left of its name or on None if you do not want to allow any associated element", "Default ITIL templates: default templates for Tickets, Changes and Problems that will apply for profile.", "Default ITIL templates", "See hardware of my groups: asset whose type is authorized and for which I am a member of the group." ] }, { "title": "Standard interface", "items": [ "Common fields with the simplified interface will not be detailed. The 7 standard permissions will not be listed (see Permissions description ).", "Tickets permissions +++++++++++++++++++", "Tickets permissions", "Be in charge: be assigned to a ticket. All the users of this profile having this option enabled will be present in the list of technicians who can be assigned to a ticket.", "Steal: become the technician assigned to the ticket. In this case, the list of technicians who can be assigned to the ticket will only include the name of the person connected.", "Change the Priority: change the priority in order to make an incident a Major priority, among other things. Modifying the priority therefore cancels the automatic calculation defined in the general configuration.", "See All Tickets: see all tickets created in the entity.", "See Assigned: see tickets for which I am the technician or having one of my groups as group of technicians.", "Assign: add a technician, a group of technicians or a supplier to a ticket.", "View new tickets: see incoming tickets that have no technician assigned yet.", "Followups permissions +++++++++++++++++++++", "Followups permissions", "See Private Ones: see all followups typed as private follow-up.", "Update All: modify all followups, regardless of the author.", "Add to all tickets: add a follow-up to all tickets of the entity.", "Tasks permissions +++++++++++++++++", "See Private Ones: see all the tasks typed as private task.", "Update All: modify all tasks, regardless of the author.", "Add to all tickets: add a task to all tickets of the entity.", "Planning permissions ++++++++++++++++++++", "Planning permissions", "Planning visibility permissions", "See personal planning: only see my planning data.", "See all plannings: see the data of all plannings", "See schedule of people in my groups: see the data of the plannings of the members of my groups.", "Depending on the permissions of the profile, you can see the notes published in the planning as well as the tasks of a ticket, a problem or a change.", "Problems permissions ++++++++++++++++++++", "See (author): view problems for which I am a requester, or a member of the requesting group, or an observer, or a member of the observer group, or the assigned technician, or member of the assigned group.", "This permission allows also to:", "see the Costs tab,", "see the Tasks tab,", "create a task if I am the assigned technician or member of the assigned group", "resolve the problem if I am the assigned technician or assigned group member.", "See All: see all the data of a problem.", "Changes permissions +++++++++++++++++++", "Changes permissions", "See (author): see the changes for which I am the requester, or member of the requesting group, or observer, or member of the observer group, or the assigned technician, or member of the assigned group.", "This permission also allows to:", "see the Costs tab,", "see the Tasks tab,", "create a task if I am the assigned technician or member of the assigned group", "resolve the change if I am the assigned technician or assigned group member.", "See All: see all the data of a change.", "Validation permission:", "Create: send a validation request", "Purge: delete a validation request", "Validate: respond to a validation request. Having this right makes you appear in the list of people who can validate.", "The Validation tab will only be displayed in the ticket if you have one of the Validation permissions." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/assistancetab.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/profiles/assistancetab.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/assistancetab.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0022", "title": "Setup permissions", "category": "administration", "tags": [ "glpi", "documentation", "administration", "configurationtab" ], "relatedIssuePatterns": [ "administration", "configurationtab" ], "summary": "The 7 standard permissions will not be listed (see Permissions description ).", "sections": [ { "title": "Overview", "items": [ "The 7 standard permissions will not be listed (see Permissions description )." ] }, { "title": "All Configuration Permissions", "items": [ "All Configuration Permissions", "The Search result display permission allows to configure the displayed columns in the GLPI search engine..", "User Display: display a Personal view tab allowing display customization for the user, the customization being done object by object.", "Default Display: allows to modify standard display that will apply to each user not having a personal view." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/configurationtab.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/profiles/configurationtab.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/configurationtab.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0023", "title": "User profiles", "category": "administration", "tags": [ "glpi", "documentation", "administration", "profiles" ], "relatedIssuePatterns": [ "administration", "profiles" ], "summary": "Profile is central in GLPI configuration: profile is the key for users permissions granting and for securing and isolating data.", "sections": [ { "title": "Overview", "items": [ "Profile is central in GLPI configuration: profile is the key for users permissions granting and for securing and isolating data.", "A profile is associated with :", "a user", "an entity, in a recursive or dynamic manner", "In order to enable permissions to be passed to child entities, the profile must be associated recursively.", "Different profiles can be associated with the same user, based on entities and whatever the relation between these entities: this can be achieved by adding the profile to the user for each entity where user profile must be different.", "By default, 7 profiles are pre-registered in GLPI:", "Super-Admin: This profile is granted all permissions!", "Admin: This profile has administration rights for all GLPI. Some restrictions are applied to it at the level of the configuration of rules, entities as well as other items which may alter the behavior of GLPI.", "Supervisor: This profile incorporates the elements of the Technician profile by adding elements allowing management of a team and its organization (allocation of tickets, etc.).", "Technician: This profile corresponds to the one used for a maintenance technician, having read access to the inventory and to the help desk in order to process tickets.", "Hotliner: This profile corresponds to the one that could be given for a hotline service; it allows to open tickets and follow them but not to be in charge of them as a Technician can be.", "Observer: This profile has read permission to all inventory and management data. In terms of assistance, it can open a ticket or be assigned one, but cannot administer this section (assign a ticket, steal a ticket...).", "Self-Service: This profile is the most limited. It is also the only one to have a different interface, the simplified interface, as opposed to the standard interface. However, it can declare a ticket, add a follow-up, consult the FAQ or reserve asset. This profile is set as the default profile." ] }, { "title": "Permissions description", "items": [ "Once the profile has been created, it will be possible to establish the permissions on the various functionalities of GLPI. Seven tabs corresponding to the different menus of GLPI are then available to manage this set of permissions and are described below.", "The different permissions of an object are listed on the line of its name. To activate an permission, the corresponding box must be checked and vice versa to delete an permission the box must be unchecked.", "Permissions after migration: migration takes over old permissions in full, regardless of the purpose, and activates the corresponding values in the new system. Previous Write permission is transformed into Read, Update, Create, Delete and Purge for most objects and must then be refined if needed. For others, the permissions are grouped by object, for example, FAQ permission are permissions of the Knowledge Base object.", "Some permissions are standards for all objects:", "Read: allows to display an object, it is also often this permission which displays or not the object in the different menus", "Update: allows to display an object data", "Create: allows to create a new element of the type of the object", "Delete: allows you to place the object in the trash bin. If this permission is not present, it means that the object does not have a trash bin.", "Purge: deletes the object from the trash bin and therefore permanently from the database. The permissions can therefore be refined between temporary deletion (placing in the trash bin) and permanent deletion (purging the trash bin)", "Read notes: allows to display the Notes tab, if object has one", "Update notes: allows to modify the content of a note or to delete it" ] }, { "title": "Assets", "items": [ "The 7 standard permissions described above apply to the elements of tab Assets.", "Permissions on assets", "The Internet permission applies to:", "IP field of a network port", "association or disassociation of a network name to a network port", "Internet part of dropdowns (IP networks, internet domains, WiFi networks, network names)" ] }, { "title": "Assistance", "items": [ "This tab manages permissions on tickets, follow-ups, tasks, validations, associations, problems and changes. It also manages the visibility of statistics and schedules as well as the assignment of a template to the profile.", "See Tab \"Assistance\"" ] }, { "title": "Life cycle", "items": [ "This tab manages the permissions on the status life cyle of tickets, problems and changes.", "See Tab \"Life cycle\"" ] }, { "title": "Management", "items": [ "The 7 standard permissions described above apply to the elements of tab Management.", "Permissions on management", "The permissions on Financial and administrative information applies also to objects containing financial information; for instance it is not allowed to purge a computer containing financial information if profile is not granted with Purge permission on financial information." ] }, { "title": "Tools", "items": [ "This tab manages permissions on notes, RSS feeds, public bookmarks, reports, reservations, knowledge base as well as projects and tasks of a project.", "See Tab \"Tools\"" ] }, { "title": "Administration", "items": [ "This tab manages permissions on users, entities and business rules on tickets.", "See Tab \"Administration\"" ] }, { "title": "Configuration", "items": [ "See Tab \"Configuration\"" ] }, { "title": "Users", "items": [ "This tab lists the entities in which this profile is assigned. To see the corresponding users, click on the concerned entity. \"D\" means the permissions have been assigned dynamically, \"R\" means the permissions are recursive from the assignment entity." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/profiles.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/profiles/profiles.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/profiles.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0024", "title": "Tools Permissions", "category": "administration", "tags": [ "glpi", "documentation", "administration", "toolstab" ], "relatedIssuePatterns": [ "administration", "toolstab" ], "summary": "The 7 standard permissions will not be listed (see Permissions descriptions ).", "sections": [ { "title": "Overview", "items": [ "The 7 standard permissions will not be listed (see Permissions descriptions )." ] }, { "title": "Simplified Interface", "items": [ "Read the FAQ: see the knowledge base articles which are published in the FAQ.", "Make a Reservation: reserve an asset." ] }, { "title": "Standard Interface", "items": [ "Common fields with the simplified interface will not be detailed.", "Tools permissions", "Knowledge Base Permissions ++++++++++++++++++++++++++", "Knowledge Base Administration: administer knowledge base access.", "Publish in the FAQ: add or remove an article from the FAQ.", "Projects Permissions ++++++++++++++++++++", "See (Actor): see the projects I have created or for which I am the supervisor or member of the supervisor group.", "See All: see all the entity's projects.", "Tasks Permissions +++++++++++++++++", "See (Actor): see the tasks I created.", "Update (Actor): modify the tasks that I have created or for which I am a member of the team." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/toolstab.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/profiles/toolstab.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/profiles/toolstab.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0025", "title": "Rules for assigning an item to an entity", "category": "administration", "tags": [ "glpi", "documentation", "administration", "inventorytools" ], "relatedIssuePatterns": [ "administration", "inventorytools" ], "summary": "GLPI has a type of rules that automatically assign an item from an inventory tool to an entity and a location.", "sections": [ { "title": "Overview", "items": [ "GLPI has a type of rules that automatically assign an item from an inventory tool to an entity and a location.", "A certain number of criteria are available: those containing generic fields (name, description, serial number, domain, IP address, subnet) but also fields coming from the inventory tool if the tool provides them.", "The available actions are:", "ignore import", "assign to an entity", "assign to an entity using value from regular expression", "assign to a location.", "The engine stops at the first matching rule. It is therefore necessary to carefully order the list of rules. In addition, it is preferable to put the rules which are most likely to be verified first, for example for entities containing a lot of assets. The rules for assignment to an entity are only played during the initial import of the machine into GLPI, which means that once a machine is imported, there is no automated process to change its entity and that manual transfer must be used.", "Using GLPI blacklist mechanism, it is possible to exclude certain values from processing by the rules engine such as certain IP or MAC addresses, for example an IP 127.0.0.1; see Blacklists ." ] }, { "title": "Rules for importing and linking computers", "items": [ "A specific rules engine allows to control the process of importing and binding machines from an inventory tool. This engine defines rules that allow to import, link or refuse computers.", "How a computer is imported:", "computer to be imported pass through the entity assignment engine. If it does not return any entity, then the machine is not imported. Otherwise, the process continues.", "computer pass through the import and link engine. Depending on the rules, it is either imported into its destination entity, or linked with another present in GLPI, or not imported.", "A certain number of criteria are available: generic fields (name, description, serial number, domain, IP address, subnet) but also fields coming from the inventory tool if the tool provides them, the destination entity of the machine as well as a status used to search for a machine already present in GLPI.", "The possible actions are to ignore the import, to link it if possible, if not to import it if possible otherwise to refuse the import.", "Refuse all imports coming from a precise inventory server:", "if inventory server is server1 then refuse import yes", "Linking machine:", "if machine to import : serial number is already present in GLPI yes AND Lookup computers in GLPI which status is in stock then link assign link if possible, else no import", "Refuse a computer because of wrong serial number:", "if machine to import : serial number is \"To be Filled By OEM\" then link refuse import yes" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/inventorytools.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/rules/inventorytools.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/inventorytools.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0026", "title": "Rules", "category": "administration", "tags": [ "glpi", "documentation", "administration", "rulesmanagement" ], "relatedIssuePatterns": [ "administration", "rulesmanagement" ], "summary": "Export, import and duplication is possible for all rules. These operations can be carried out globally from the main rules page or by batch from the search engines for the various rules via massive actions. These features are interesting for example in the context of switching of rules from a pre-production environment to a production environment.", "sections": [ { "title": "Overview", "items": [ "Export, import and duplication is possible for all rules. These operations can be carried out globally from the main rules page or by batch from the search engines for the various rules via massive actions. These features are interesting for example in the context of switching of rules from a pre-production environment to a production environment." ] }, { "title": "Rules engine", "items": [ "GLPI contains a rules engine which enables a certain number of actions and associations to be carried out automatically.", "This engine is used for both:", "management rules:", "assigning an asset to an entity", "granting permissions to a user", "assigning category to a software", "routing tickets to entities", "automatic actions when opening ticket", "data dictionaries :", "manufacturers", "software", "printers", "types of assets", "models of assets", "operating system related fields", "The engine behaves differently depending on the types of rules:", "stop after first matching rule", "apply all rules", "apply rules and pass rule result to next rule", "Rules can be disabled, for example when writing and testing new rules." ] }, { "title": "Rules for assigning a ticket opened via a mail collector", "items": [ "See Rules for assigning a ticket opened via a mail collector" ] }, { "title": "Rules for assigning authorizations to a user", "items": [ "See Rules for assigning authorizations to a user" ] }, { "title": "Rules for assigning a category to software", "items": [ "Classification by category makes it easier to display and find software. This can be done automatically for any new software, or retroactively. The available criteria are the publisher, the name and the comment of the software. The only possible action is to assign software to a category. It is possible to replay the rules from the software list, using massive action Recalculate category." ] }, { "title": "Business rules for tickets", "items": [ "When opening or modifying a ticket, a mechanism allows to modify ticket attributes automatically.", "See Business rules for tickets" ] }, { "title": "Rules for inventory agent", "items": [ "The two menus below are only visible if you use an inventory agent for an automatic inventory of computers in GLPI.", "rules for assigning an item to an entity", "rules for importing and linking computers", "See Rules for inventory agent", "Transfer This menu allows you to define the inter-entity transfer profiles.", "Several actions are possible:", "Preserve: the item will be transferred with the object;", "Put in Trash Bin: the item will be placed in the recycle bin of the ceding entity;", "Delete Permanently: the item will be deleted from the database;", "Keep: the item will remain in the ceding entity;", "Disconnect: the connection between element and object will be deleted", "Blacklists Thanks to the GLPI blacklist mechanism, it is possible to exclude certain values from processing by the rules engine. The types that can be taken into account are:", "IP address;", "MAC address;", "serial number;", "UUID;", "email", "This allows, for example, to exclude certain IP addresses from the inventory agent (for example an IP 127.0.0.1 or 0.0.0.0) or not to create a ticket from a particular email address (for example daily backup of a server)." ] }, { "title": "Create a rule", "items": [ "A rule is composed of a series of criteria. Depending on the option chosen (OR/ ND) one or all of the criteria must be verified to trigger an action list.", "A preview mechanism allows you to test the rules being written before putting them into production.", "Several criteria are available:", "simple:", "is", "is not", "contains", "does not contain", "starts with", "ends with", "under (for tree dropdowns, indicates to be this dropdown or one of the child dropdowns)", "not under (for tree dropdowns, indicates not to be this dropdown or one of the child dropdowns))", "complex:", "regular expression match", "regular expression does not match", "Regular expressions (otherwise known as regex) return one or more results which can then be used by actions using the #x directive (where x is the number of the result of the regular expression).", "Criteria : name matching regular expression `/DESKTOP\\_(.\\)/ If object is named DESKTOP_0001, then it will be possible to use 0001 in the actions of the rules using parameter #0`", "KEEP ?", "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.) In our example, we're going to create a rule that takes the inventory tag into account. If the tag is France, then apply the Paris location", "In administration > Rules > Location Rules", "Click + Add", "You can add different information (name, logical operator, comments, description, active)", "\"OR\" the rule will then apply from the 1st corresponding criterion. It will ignore all subsequent criteria.", "\"AND\", on the other hand, will have to take all the criteria into account for the rule to be applied.", "Active your rule", "Clik + Add", "In Criteria, click Add a new criterion", "Select Agent > Inventory tag", "Enter France", "Click + Add", "In Actions tab, click Add a new action", "Select the location to assign", "Click + Add", "You can test the rule location by clicking on Test rules engines in Administration > Locations rules" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/rulesmanagement.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/rules/rulesmanagement.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/rulesmanagement.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0027", "title": "Business rules for tickets", "category": "administration", "tags": [ "glpi", "documentation", "administration", "ticketbusinessrules" ], "relatedIssuePatterns": [ "administration", "ticketbusinessrules" ], "summary": "A mechanism is available to modify the attributes of the ticket automatically when a ticket is opened or updated.", "sections": [ { "title": "Overview", "items": [ "A mechanism is available to modify the attributes of the ticket automatically when a ticket is opened or updated.", "The available criteria are all the attributes of the ticket (title, description, status, category, urgency, impact, priority, source of the request, type of asset, group/user/location requesters, assigned to supplier/group/technician, type of asset, entity) as well as others related to email collectors (headers ...).", "The possible actions are to modify certain attributes of the ticket (status, category, urgency, impact, priority, requesters group/user/location, assigned to supplier/group/ technician). It is also possible to assign a ticket to a device according to data present in the ticket (attribution on the IP address, the full name and the domain, the MAC address) or even send a validation request.", "When using GLPI in multi-entities, the business rules for the tickets can be recursive, i.e. they can be defined on an entity with an application on the entity itself and on the sub-entities.", "Three tabs are available:", "applied rules (entity name): all the rules of the parent entities played (only if you have the authorization Business rules (parent) on the authorization Business rules for tickets (entity);", "local rules: the list of rules defined for the current entity;", "rules applicable in sub-entities: all the rules applied after those of the current entity.", "Special case for the Emergency and Impact fields", "If you define an emergency and/or an impact via a business rule, you should also consider adding the Recalculate priority action so that it is based on the fields you have just defined." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/ticketbusinessrules.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/rules/ticketbusinessrules.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/ticketbusinessrules.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0028", "title": "Rules for assigning authorizations to a user", "category": "administration", "tags": [ "glpi", "documentation", "administration", "userauthorizations" ], "relatedIssuePatterns": [ "administration", "userauthorizations" ], "summary": "GLPI has a dynamic authorization engine which is based on external authentication sources.", "sections": [ { "title": "Overview", "items": [ "GLPI has a dynamic authorization engine which is based on external authentication sources.", "An authorization in GLPI results from the attribution of permissions over a scope (one or more entities); it is the joint membership to a profile and to an entity.", "Authorizations can be assigned statically, by assigning a user to a profile in an entity; however this is not the recommended method.", "It is recommended to use the entity and permissions assignment rules engine to automatically assign permissions. This requires using an external authentication.", "The engine executes all the rules and does not stop after the first rule that applies to the user. Several rules thus make it possible to assign different authorizations to the same user. A user with several authorizations can, during his session and according to his activities, change profile and entity context." ] }, { "title": "Default profile", "items": [ "If a default profile is defined in the configuration of GLPI profiles, and if an authorization assignment rule does not include a profile assignment, then the default profile is used when assigning a user to the entity.", "If no default profile is defined, the user is imported without authorization: he is neither assigned to an entity, nor assigned to a profile. Only the super-admin profile can see it in the root entity." ] }, { "title": "Mail server based authorizations", "items": [ "IMAP/POP email information can be used to automatically assign permissions. The IMAP/POP identifier (the user's login) and the URL of the mail server can be used as criteria. Users can be created on the fly when they log in. On the other hand, it is not possible to do a bulk import from the mail server." ] }, { "title": "Mail server URL based authorizations", "items": [ "When multiple mail servers are defined as the authentication source and the mail server URL is a relevant criterion, this information can be used to define authorizations.", "Authentication uses the following IMAP/POP servers: `imap.exemple.fr et imap.exemple.be. Each server is defined as an authentication source. This information allows to assign user to France or Belgium` entities. To achieve that, two static rules are necessary:", "Rule for Belgium:", "Criteria: IMAP/POP is `imap.exemple.be`", "Actions: assign entity Belgium", "Rule for France:", "Criteria: IMAP/POP is `imap.exemple.fr`", "Actions: assign entity France" ] }, { "title": "Email identifier based authorizations", "items": [ "When the users' e-mail addresses contain several domain names, or information relevant to defining the authorizations, this information can be used to define the authorizations. It is also possible to assign an entity to a user using the mail domain if this is specific to an entity. The email domain used by the entity is defined in the advanced information for entities .", "Users authenticate using e-mail addresses of the following form: `user@example.fr and user@example.be. It does not matter if one or more mail servers are used for authentication. This information is used to assign the user to the France or Belgium` entity. For this purpose two static rules will be necessary:", "Rule for Belgium:", "Criteria: IMAP/POP identifier ends with `exemple.be`", "Actions: assign entity Belgium", "Rule for France:", "Criteria: IMAP/POP identifier ends with `exemple.fr`", "Actions: assign entity France" ] }, { "title": "Authorizations based on LDAP directories", "items": [ "A user's LDAP attributes can be used as a source to dynamically assign permissions to that user using permission assignment rules. There are many ways to use an LDAP tree to create authorization rules for users, best solution depend on the context of the directory implementation." ] }, { "title": "Authorizations based on organizational units of an LDAP directory", "items": [ "Given an LDAP directory where the organization of branches (organizational units) corresponds to the organization of GLPI entities. Each organizational unit (ou) contains the users, either directly or in a sub-branch. Each of the branches can be used to establish a rule for assigning a user to an entity. The case of users belonging to several entities must be dealt with elsewhere. This model is relevant when a default profile can be assigned to the majority of users. The assignment of non-standard profiles should be dealt with elsewhere. The information on the user sent from the directory is sufficient to create the assignment rules in GLPI.", "Consider an LDAP tree of the following form:", "org +- exemple +- france +- paris +- lyon +- bordeaux +- belgique +- bruxelles", "Each of the branches is formalized as in the following example: `ou=lyon,ou=france,dc=exemple,dc=org`", "In the configuration of each entity, in the advanced information tab, indicate the LDAP information representing the entity (in this case the \"distinguished name\" of the entity).", "For example, for the Lyon entity: LDAP information representing the entity: `ou=lyon,ou=france,dc=example,dc=org`. Then, define the rule(s) in Administration > Rules > Entity and rights assignment rules.", "The user has two options: a static rule set or an adaptive rule.", "Static rule: for each entity, define an assignment rule of the following form:", "Criteria: (LDAP)DistinguishedName ends with: `ou=lyon,ou=france,dc=exemple,dc=org`", "Actions: assign entity lyon", "Adaptive rule: a single rule based on regular expressions is sufficient to define the assignment to all entities:", "Criteria: (LDAP)DistinghuishedName matches following regular expression: `/(ou=.)/`", "Actions: assign entity from LDAP, value from regular expression: `#0`", "or even", "Criteria: (LDAP)DistinghuishedName matches following regular expression: `/(ou=.)/`", "Actions: assign entity full name value from regular expression: Root entity > `#0`", "Running the rule retrieves its organizational unit (`ou`) from the user's distinguished name. It will then compare it to the values of the LDAP Information attribute representing the entity in the database. If an entity has the attribute whose value matches, then that attribute is used as the result of the rule." ] }, { "title": "Authorizations based on groups or attributes of a user in an LDAP directory", "items": [ "In the directory, each user is part of a group corresponding to a GLPI profile and of a group corresponding to an entity. A user can be part of several profiles and several entities. Depending on the directory configuration, the information of the user's group membership can be found in the user object or in the group object.", "In the first case, the information contained in the user object is sufficient to create authorization rules: it is not necessary to import the groups from the directory into GLPI", "In the second case, the information contained in the user object is not sufficient and it is necessary to retrieve the information on the groups. You must first configure the LDAP groups and the automatic linking of users to groups.", "Consider an LDAP tree of the following form:", "org +- exemple +- profil += post-only += tech += admin += super-admin +- entité +- france += paris += lyon +- people +-", "In this example, profiles and entities are defined as groups. For example: `cn=post-only,ou=profil,dc=exemple,dc=org ou cn=paris,ou=entité,dc=exemple,dc=org`", "No specific entity configuration is required.", "In Administration > Rules > Entity and rights assignment rules, define the following rules:", "for assigning a profile to a user:", "Criteria: Group directory LDAP is post-only", "Actions: Profile assign post-only", "for assigning to an entity:", "Criteria: Group directory LDAP is paris", "Actions: Entity assign Exemple > France > Paris" ] }, { "title": "Using different sources of authorization", "items": [ "Mixed cases can be encountered: the rules can use both membership of organizational units for assignment to an entity, and membership of a group for assignment to a profile." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/userauthorizations.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/rules/userauthorizations.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/rules/userauthorizations.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0029", "title": "Authorizations", "category": "administration", "tags": [ "glpi", "documentation", "administration", "authorizations" ], "relatedIssuePatterns": [ "administration", "authorizations" ], "summary": "Authorizations correspond to the rights and permissions assigned to users or groups to access different features or modules. They allow you to precisely define who can view, create, modify, or delete data (tickets, assets, budgets, etc.). Authorizations are managed via profiles and ensure security, confidentiality, and the proper distribution of responsibilities in the management of the GLPI environment.", "sections": [ { "title": "Overview", "items": [ "Authorizations correspond to the rights and permissions assigned to users or groups to access different features or modules. They allow you to precisely define who can view, create, modify, or delete data (tickets, assets, budgets, etc.). Authorizations are managed via profiles and ensure security, confidentiality, and the proper distribution of responsibilities in the management of the GLPI environment.", "You will be able to see in the \"profiles\" section as in the example above the letters R and D.", "R = Recursive", "This means that the profile has access to all attached child entities.", "D = Dynamic", "This means that the authorization was added through an authorization rule. If this rule is modified, the authorization will also be changed the next time the user logs in." ] }, { "title": "Add an authorization", "items": [ "To add an authorization, select :", "the entity", "the profile", "the recursion" ] }, { "title": "Delete an authorization", "items": [ "To delete an authorization use the massive action." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/users/tabs/authorizations.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/users/tabs/authorizations.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/users/tabs/authorizations.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0030", "title": "Users", "category": "administration", "tags": [ "glpi", "documentation", "administration", "users" ], "relatedIssuePatterns": [ "administration", "users" ], "summary": "The Users tab allows you to manage their information (mail, name, authorization, etc.).", "sections": [ { "title": "Overview", "items": [ "The Users tab allows you to manage their information (mail, name, authorization, etc.).", "You can import users. You can refer to import users", "It is possible to deactivate a user if needed. If deactivated, the user can no longer be selected in drop-down menu for tickets or inventories, but keeps associated items and tickets. Validity dates can also define the activity time slot of user: the user account will be considered as active only after the start date and/or before the end date. Both dates can be defined independently.", "A photo can be added manually or imported automatically from a directory (see Authenticate users with LDAP )." ] }, { "title": "Impersonate", "items": [ "For debugging or administrative purposes, it's possible for a “super-admin” account (or any profile with the configuration rights) to temporarily take the ownership of another user’s account without knowing its password. An icon is available at the top of the user´s form to perform this action.", "To note:", "A special banner will show permanently as long as the function is active and will allow you to exit this mode.", "After the exit, the user will retrieve its session as it was before using the feature.", "The history of actions taken by the administrator will appear with a special note: “user (xxx) impersonated by admin (yyy)”.", "For example, a technician with this right could impersonation self-service users but not admins. This is mainly to avoid privilege escalation." ] }, { "title": "Vcard", "items": [ "You can download a user vcard by this icon :", "In a display form, the following information is available:" ] }, { "title": "User Information", "items": [ "Login : Used to log in to GLPI.", "Surname", "Firstname", "Timezone: by default \"use server configuration\". If timezone are not active, go to timezone", "Active", "Valid since", "Valid until", "Authentication : Indicates the authentication source (internal database, LDAP or other)", "Category", "Title", "Comments", "Administrative number", "Location", "Default profile", "Default entity", "Default group", "Supervisor" ] }, { "title": "Contact information", "items": [ "Emails", "Phone", "Mobile phone", "Phone2" ] }, { "title": "Password and access keys", "items": [ "API token", "Password", "() If the user was imported by a provider (LDAP, SCIM, etc.), this information cannot be modified manually." ] }, { "title": "Authorizations", "items": [ "This tab allows to manage user authorizations . A summary tab displays already attributed authorizations for the user." ] }, { "title": "Groups", "items": [ "This tab lists the groups associated to the user. Table includes group name, whether the group is dynamic (i.e. linked to a directory service), whether the user is delegatee or manager for the group.", "If modify user authorization is granted, it is also possible from this tab to assign a group to the user.", "For more details, go to Manage groups" ] }, { "title": "Settings", "items": [ "This tab allows to edit user's settings (see Manage settings ). In order to be able to modify data in this tab, general configuration modification authorization must be granted.", "Information modified from this tab takes priority over the general configuration of glpi" ] }, { "title": "Documents", "items": [ "It is possible to add documents to user files" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/users/users.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/users/users.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/users/users.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0031", "title": "Import users", "category": "administration", "tags": [ "glpi", "documentation", "administration", "usersimport" ], "relatedIssuePatterns": [ "administration", "usersimport" ], "summary": "From users list, three options are available for adding a user |addUserAll|:", "sections": [ { "title": "Overview", "items": [ "From users list, three options are available for adding a user |addUserAll|:", "Add user: Opens a user creation form, similar to the Add button; requires profile to be granted user creation authorization", "...From an external source: Import users from external source", "LDAP directory link: Import and synchronize users from LDAP directory" ] }, { "title": "Import users from external source", "items": [ "This button is available when profile is granted user External add authorization. The identifier of a user being known, GLPI allows to search user and to import user's authentication information from an external source. Once user's connection identifier filled, this identifier is search in available directories (button Import from directories) or in other sources (button Import from other sources).", "if more that one user is identified by provided identifier, then adding is not performed", "when using a mail directory for authentication, no import user list is available", "User personal information can be imported under some conditions from a LDAP directory; users imported from a mail server do not get personal information." ] }, { "title": "Import and synchronize users from LDAP directory", "items": [ "This button is available when profile is granted user External add authorization. GLPI allows users advanced search in a LDAP directory. The interface is restricted to the list of entities for which GLPI connected user is granted authorization (see Administer user profiles ). Once entity is selected (if GLPI is in multi-entities mode or if connected user is granted authorization for several entities), a list of criteria is displayed, based on personal information collected from directory. The search syntax for fields is similar to the syntax of GLPI search engine (see Search ). Search can be limited to users added or modified in the directory during given time slot by following link Activate date filtering.", "In order to be able to use simplified interface, either LDAP parameters for the entity must have been configured first using Administration > Entity to assign a directory to the entity or a default directory must have been defined.", "This option, coupled with search on criteria, allows to bypass the limit of records returned by directory for a LDAP request (see Authenticate users with LDAP directories)", "Simplified interface does not require write authorization for users. An asset manager or a technician can therefore import users from the directory without having access to these imported users after import. This option is for example useful for a call center or for a directory from which mass users import is not desired.", "An Expert Mode is also proposed by following link on the right of table header. This mode is available for users granted with update authorization either for general configuration or for entities. Unlike simple interface, results are not filtered by entity: the only available criteria are directory, based and users search filter.", "Once imported from a directory, GLPI stores user's LDAP unique identifier (the distinguedName or DN) in addition to connection identifier. This allows to manage updating connection identifier when DN is left untouched. For example, if connection identifier is email address, GLPI will be able to update it without recreating a new user in the case of a change.", "If an external authentication source is configured, it becomes possible to import and synchronize users using this source. For regular maintenance of the users base, it is recommended to use the GLPI CLI command glpi:ldap:synchronize_users. For daily management, the manual import mechanism is available (see above)." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/users/usersimport.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/administration/users/usersimport.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/administration/users/usersimport.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0032", "title": "Asset Definitions", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "asset-definitions" ], "relatedIssuePatterns": [ "configuration", "asset-definitions" ], "summary": "Since GLPI 11, the generic asset plugin has been integrated into GLPI natively. This makes it possible to create customised asset types to suit your needs.", "sections": [ { "title": "Overview", "items": [ "Since GLPI 11, the generic asset plugin has been integrated into GLPI natively. This makes it possible to create customised asset types to suit your needs." ] }, { "title": "Migration generic objects to asset definitions", "items": [ "When migrating your instance to GLPI 11, the generic objects plugin must be installed. Once the migration is complete, enter the command in CLI mode from your GLPI folder:", "php bin/console migration:genericobject_plugin_to_core" ] }, { "title": "Definitions", "items": [ "Asset definitions can be used to add assets that are not natively available. For example, you can add servers or laptops separately from the native Computers type. Each custom asset could be configured to behave like any other asset via capacities." ] }, { "title": "Create an asset", "items": [ "To add a new asset, click on + Add", "Fill in the information for the new asset", "Label (this field will appear in the list of assets)", "System name (it cannot be changed later)", "Comments", "Active", "Icon", "Examples: API calls, webhooks, etc. It can be personnalized, but some words are reserved such as classes from GLPI like Computer, Monitor, etc. Items linked to the system name \"Example\" will have the class \"Glpi\\CustomAsset\\ExampleAsset\"", "After the creation, an error message appears: There is currently no profile with access to items with current definition You need to go to profiles" ] }, { "title": "Capacities", "items": [ "Capacities lets you add behaviors such as the ability to link software, network ports, contacts, etc. to the asset. Each asset can be selected and customised as required.", "List of the behaviors/elements that can be linked:", "Antiviruses", "Appliances", "Certificates", "Components", "Connections", "Contracts", "Databases instances", "Documents", "Domains", "Financial and administrative information", "Global search", "Historical", "Impact analysis", "Inventory", "Knowledge base", "Manual links / External links", "Network ports", "Notes", "Operating systems", "Plugs", "Projects", "Racks", "Remote management", "Reservations", "Sockets", "Software", "Virtualization", "Volumes" ] }, { "title": "Fields", "items": [ "The fields tab is used to add additional fields and and hide, or reorder native ones. You can customise them by indicating whether they should be text, URL, date, etc." ] }, { "title": "Create a custom field", "items": [ "To add a new field, click on + New field", "Fill in the required fields", "Label: name which will be displayed on the asset form, search results, etc", "System name: The system name field corresponds to what will be used when development is involved. Examples: API calls, webhooks, etc.", "In the legacy API, the field name is prefixed by `custom_`; to avoid conflicts with standard fields.", "Type: string, date, URL, dropdown, yes/no, text, date and time, number. Cannot be modified once saved", "Full width: indicates the field will be extended along the entire length of the form", "Mandatory: make it mandatory or not to fill in the field before saving the asset", "Readonly for these profiles: select one or more profiles with read-only access to this field.", "The permissions in the profiles tab take precedence over this field.", "Hidden for these profiles: select one or more profiles whose fields will be hidden", "The authorisations in the profiles tab take precedence over this field. It will therefore be visible to a profile even if it is selected in this field.", "Default values: specify a default value", "Computers", "Monitors", "Network devices", "Peripherals", "Phones", "Printers", "Licenses", "Certificates", "Unmanaged assets", "Appliances", "Custom Assets", "Locations", "Statuses of items", "Manufacturers", "Blacklists", "Blacklisted mail content", "Default filters", "ITIL categories", "Task categories", "Task templates", "Solution types", "Solutions templates", "Approval templates", "Request sources", "Followup templates", "Project states", "Project types", "Project tasks types", "Project tasks templates", "External events templates", "Event categories", "Pending reasons", "Service catalog categories", "Approval steps", "Computer types", "Networking equipment types", "Printer types", "Monitor types", "Devices types", "Phone types", "License types", "Cartridge types", "Consumable types", "Contract types", "Contact types", "Generic types", "Sensor types", "Memory types", "Third party types", "Interface types (Hard drive...)", "Cases types", "Phone power supply types", "Files systems", "Certificate types", "Budget types", "Simacard types", "Line types", "Rack types", "PDU types", "Passive device types", "Cluster types", "Database instance type", "Custom Asset types", "Computer models", "Networking equipment models", "Printer models", "Monitor models", "Peripheral models", "Phone models", "Device camera models", "Device case models", "Device control models", "Device drive models", "Device generic models", "Device graphic card models", "Device hard drive models", "Device memory models", "System board models", "Network card models", "Other component models", "Device power supply models", "Device processor models", "Device sound card models", "Device sensor models", "Rack models", "Enclosure models", "PDU models", "Passive device models", "Custom Asset models", "Virtualization systems", "Virtualization models", "States of the virtual machine", "Document heading", "Document types", "Business criticies", "Databse instance categories", "Knowledge base categories", "Calendars", "Close times", "Operating systems", "Versions of the operating systems", "Service packs", "Operating systems architectures", "Editions", "Kernels", "Kernels versions", "Update sources", "Networking interfaces", "Networks", "Network port types", "VLANs", "Line operators", "Domain types", "Domain relations", "Records types", "Fiber types", "Cables types", "Cable strands", "Socket models", "IP networks", "Internet domains", "Wifi networks", "Network names", "Software categories", "Users titles", "User categories", "LDAP criteria", "Ignored values for the unicity", "Fields storage of the login in the HTTP request", "Plugs", "Appliance types", "Appliance environments", "Resolutions", "Image formats", "USB vendors", "PCI vendors", "Webhook categories", "Custom dropdowns" ] }, { "title": "Delete a custom field", "items": [ "To delete a custom field, click on the hide icon", "Then, click on the trashbin icon. Note that this action is irreversible" ] }, { "title": "Hide or show a field", "items": [ "Each field can be hidden in the asset form.", "To hide a field, click on the hide icon", "To restore an hidden field, drag and drop this field in the list" ] }, { "title": "Modify a field", "items": [ "You can change all the fields, but some information cannot be changed in a default field.", "In a default field, you can modify:", "Full width", "Mandatory", "Readonly for these profiles", "Hidden for these profiles", "In a custom field, you can modify:", "Label", "System name (will be modified automatically when changing the label)", "Full width", "Mandatory", "Readonly for these profiles", "Hidden for these profiles", "Default value" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/asset_definitions/asset_definitions.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/asset_definitions/asset_definitions.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/asset_definitions/asset_definitions.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0033", "title": "Configure external authentication", "category": "configuration", "tags": [ "glpi", "documentation", "configuration" ], "relatedIssuePatterns": [ "configuration", "configuration" ], "summary": "This menu allows you to configure the general settings for integration with external authentication sources.", "sections": [ { "title": "Overview", "items": [ "This menu allows you to configure the general settings for integration with external authentication sources.", "In order to be able to use these external authentication sources, the corresponding extensions must first be activated in the PHP configuration. There is no limit to the number of external sources configured in the application.", "To use the capacity of GLPI to create on the fly users present in the external sources of authentication, it is necessary to activate it in the menu Configuration \\> Authentication \\> Configuration.", "The LDAP directories also allow you to refuse the creation of users who do not have authorizations. Deleting a user from the directory can also lead to an action such as trashing the user, deleting his permissions or deactivating him. You also have the option to specify how to handle users that were previously deleted from the directory but are now restored. You can set the restore action to do nothing, restore the user from the trashbin, or re-enable the user.", "It is also at this level that the time zone of GLPI is set.", "External authentication sources that can be used inside GLPI are:", "LDAP directories", "Email servers", "CAS server", "x509 certificate", "Delegate authentication to web server" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/configuration.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/authentication/configuration.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/configuration.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0034", "title": "Authenticate from IMAP", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "imap" ], "relatedIssuePatterns": [ "configuration", "imap" ], "summary": "The interfacing of GLPI with mail servers as a source of authentication.", "sections": [ { "title": "Overview", "items": [ "The interfacing of GLPI with mail servers as a source of authentication.", "This authentication source is configured from the menu `Setup > Authentication > Mail servers`.", "This ability can compensate for the absence of directory or of CAS server. However, contrary to what is possible with other sources of other authentication sources, no mass import is available. A user is authenticated by GLPI if the server of mail server has authenticated him beforehand.", "The connection to the mail server uses the IMAP or POP protocols. The options of SSL and TLS encryption are available. The distinction is made between the mail domain which is the part of the of the mail address that follows the asterisk character, and the fully qualified name of the mail server, which can serve several mail domains." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/imap.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/authentication/imap.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/imap.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0035", "title": "LDAP directories", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "ldap" ], "relatedIssuePatterns": [ "configuration", "ldap" ], "summary": "GLPI can interface with one or more LDAP directories in order to authenticate users, control their access, retrieve their personal information and import groups.", "sections": [ { "title": "Overview", "items": [ "GLPI can interface with one or more LDAP directories in order to authenticate users, control their access, retrieve their personal information and import groups.", "All the directories compatible LDAP v3 are supported by GLPI. It is thus also the case for the 'Active Directory of Microsoft. There is no limit as to the number of directories informed. However, the higher the number, the longer the search for a new user to authenticate can be.", "It is possible to import and synchronize users in 2 ways:", "At the first login, the user is created in GLPI. At each login, his personal information is synchronized with the directory.", "In the case where the receivers are used and there is an email not associated with an existing user, the unknown email address will be searched in the directory to create the associated user.", "In mass either via the web interface or the CLI glpi:ldap:synchronize_users command.", "If no LDAP configuration is visible (see an error message on this part) it means that the LDAP module for PHP is not installed.", "Under Linux, install the ldap package for PHP (for example php7.4-ldap on Debian), then restart the web server.", "Under Windows it is necessary to uncomment in the file php.ini (file present in the directory apache/bin) the line extension=php\\_ldap.dll then restart the Web server.", "The process of authentication of the users is divided into 3 parts: authentication, access control and finally the recovery of the personal data." ] }, { "title": "LDAP Authentication", "items": [ "At the time of the first login of the user, GLPI will search all of the configured directories until finding one that contains the user. If the option allowing to import users from an external source is active, then the user is created and the identifier of the method of connection and the LDAP server are stored in database.", "Then, at each login the user is authenticated on the directory whose identifier is stored in GLPI. The other directories are not used; If a user is deactivated in the directory which it used until then to connect, it cannot connect with another source of authentication." ] }, { "title": "Access Control", "items": [ "Access control is the assignment of permissions to a user. Even if a user is authenticated on a directory it is not necessarily entitled to connect to GLPI.", "This mechanism is based on the use of Authorization Assignment Rules." ] }, { "title": "LDAP directory", "items": [ "There is an Active Directory pre-configuration template, which pre-fills a certain number of fields.", "To load it, click on the Active Directory link when adding a directory. The Default value(s) link will reset the values to the default.", "Default server: If you have multiple LDAP servers set up, you can only define one default server. Choosing this setting will remove it from the server it was previously set to.", "Server and Port: Represent the address and port of the LDAP directory.", "GLPI can connect to an LDAP directory through an LDAPS connection. To enable this, prefix your server field with ldaps:// and change the port to the LDAPS one of your LDAP directory (default 636).", "Connection filter: Allows you to restrict the search for users in the directory. For example, if only a restricted set of users have the right to connect to GLPI, you can create a condition to restrict the search to that set of users.", "Some example filters:", "A classic LDAP filter: `(objectclass=inetOrgPerson)`", "An Active Directory filter to return only enabled users: `(&(objectClass=user)(objectCategory=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))`", "The example Active Directory filter is automatically populated when the Active Directory pre-configuration template is selected.", "BaseDN: The location in the directory from which the searches will be made.", "RootDN: The distinguished name of the user account to authenticate to LDAP with when not using anonymouse binds.", "RootDN and BaseDN are case sensitive and must not contain spaces betwen the parts. Examples:", "`cn=Admin, ou=users, dc=mycompany`: incorrect", "`cn=Admin,ou=users,dc=mycompany` : correct", "Password: The password for the account specified (if any) in the RootDN field.", "Login field: The name of the field in the LDAP directory corresponding to the user's login (Ex: `uid in LDAP or samaccountname` in Active Directory).", "Synchronization field: The name of the field in the LDAP directory used for Synchronization. This field must be unique for every user (Ex: `employeeuid in LDAP or objectguid` in Active Directory).", "The parameters to enter are simple. For example:", "Server: ldap.mycompany.fr", "BaseDN: dc=mycompany,dc=fr", "This should be enough if anonymous binds are allowed. If not, and if all users are not located within the same DN, you have to specify the DN of an authorized user and his password through the RootDN/Password parameters. For Active Directory, it is required to specify an account that has the right to authenticate on the domain.", "If some of the users have connection restrictions to certain machines configured in their Active Directory profile, a user not found error may be seen. The solution is to add the Active Directory server to the list of computers the user is allowed to connect to.", "Do not forget to activate your directory and set it as the default (if wanted) if you have multiple directories." ] }, { "title": "Test", "items": [ "Allows the testing of the configuration defined in the LDAP directory tab.", "The message Connection test successful indicates that GLPI was able to connect to the LDAP directory with the information provided (host, port, user account).", "It remains now to import the users. For that, it is necessary to check the other parameters (connection filter, login field, etc)." ] }, { "title": "Users", "items": [ "Allows you to configure how the link between the fields of the directory and those of GLPI will be made. Most of the fields are automatically mapped for you but can still be changed." ] }, { "title": "Groups", "items": [ "Allows you to configure the method for retrieving groups from the LDAP directory." ] }, { "title": "Advanced Information", "items": [ "In case the server hosting the LDAP directory is in a different timezone as GLPI, it is necessary to modify the Timezone variable to account for the difference.", "Limit of the number of records returned", "There are often two limits on the number of records returned per request.", "The client limit (defined for example on Debian/Ubuntu in `/etc/ldap/ldap.conf`)", "The server limit: If the server limit is lower than the client limit, then that is the effective limit", "If the limit is reached, the optional GLPI behavior for LDAP user deletion can not work. Moreover, GLPI will display a warning message during the import or synchronization.", "It is possible to bypass the limitation by enabling Pagination of results in the Advanced Information tab of the LDAP directory in GLPI. This will split requests into smaller requests that are under the configured limit.", "The Page size option adjusts the number of results retrieved per \"page\" with pagination enabled. The Maximum number of results option is the limit for the total number of records. This option may be useful to avoid high memory usage.", "On an OpenLDAP directory, the default limit is 500 and in Active Directory, it is 1000.", "In Active Directory it is possible to modify the value of MaxPageSize with the following commands (This modification is global for the whole directory):", "C:> ntdsutil ntdsutil: ldap policies ldap policy: connections server connections: connect to server 192.168.1.1 ( here a few messages regarding connectivity are displayed) server connections : q ldap policy : show values ( here we will see all the values including MaxPageSize which is 1000 currently) ldap policy : set maxpagesize to 5000 ldap policy : commit changes ldap policy : q ntdsutil : q" ] }, { "title": "Replicates", "items": [ "If an LDAP directory is not accessible, the users provided by it will not be able to connect to GLPI.", "To help avoid this situation, replicates can be declared in GLPI. These are LDAP servers that have the same data as the main server, but are available at a different address.", "Replicates are only used when the connection to the main server is lost. The addition of replicates in GLPI is done by entering a Name which is displayed in GLPI, as well as a Server, Port, and Timeout in the Replicates tab in the LDAP directory. To enable LDAPS," ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/ldap.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/authentication/ldap.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/ldap.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0036", "title": "Other external authentication methods", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "other" ], "relatedIssuePatterns": [ "configuration", "other" ], "summary": "The integration of GLPI and authentication sources beyond internal, LDAP, and IMAP is configured from the Setup > Authentication > Other authentication methods menu.", "sections": [ { "title": "Overview", "items": [ "The integration of GLPI and authentication sources beyond internal, LDAP, and IMAP is configured from the Setup > Authentication > Other authentication methods menu." ] }, { "title": "Central Authentication Service (CAS)", "items": [ "The configuration of a CAS server is comprised on the address of the server and its port (default 443). A base directory can be specified if needed. The return web address parameter allows you to redirect the user to a specific page after they log out from GLPI.", "Once the CAS authentication is activated, each authentication is automatically redirected to the CAS server. In order to log into an internal account or one authenticated through a different method, you have to add `?noAUTO=1` to the login URL.", "The php-curl or php-dom extensions are required to be enabled for CAS authentication to function." ] }, { "title": "x509 certificate", "items": [ "The Email attribute for x509 authentication tells GLPI to look at the value of this attribute in the `SSL\\_CLIENT\\_S\\_DN` HTTP request variable passed by the authentication system.", "It is possible to restrict the accepted values for the `O, OR, and CN` fields of the client certificate. In order to specify multiple values for each field, you may separate each value with the $ symbol." ] }, { "title": "Other automatic authentications", "items": [ "GLPI can rely on other external systems to authenticate users such as:", "Basic Apache authentication", "Windows domain authentication", "Authentication coming from an authentication server like", "LemonLDAP::NG, Shibboleth, etc", "When the user wishes to reach GLPI, this one checks the presence of a variable in the HTTP headers storing the login/username. If the variable is present, the authentication is allowed to be done. We can map the data transmitted by the authentication system with the fields of the user account of GLPI (name, first name, email, language...). To finish, the controls of authorizations are carried out. An option allows to remove the domain of the user's login (Ex: testuser@example.com > testuser).", "The list of possible names for the headers is configurable, although the most common ones are already provided by GLPI. See Configuring headings ." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/other.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/authentication/other.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/authentication/other.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0037", "title": "Receivers", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "collectors" ], "relatedIssuePatterns": [ "configuration", "collectors" ], "summary": "Receivers configuration can be reached from `Configuration -> Receivers ` menu.", "sections": [ { "title": "Overview", "items": [ "Receivers configuration can be reached from `Configuration -> Receivers ` menu.", "A receiver allow to import emails from a mailbox ans turn them into GLPI tickets. A routing mechanism will bring them to the destination entity.", "A receiver is associated with an email address. It is possible to add as many receivers as you want. Of course, the more receivers you configure, the more import will take time.", "To declare a new collector, you will have to provide a server name, as well as connection options (IMAP or POP, SSL, TLS, certificate validation). It is possible to limit the maximum size for attachments (no import, or from 1 to 100 Mio). This configuration value is inherited from the main configuration (`Setup -> General -> Assistance`) A configuration option permit to switch tickets creation date between import date or email date.", "Optionally, you can set an archive directory in the mailbox where imported and refused emails will be stored.", "Receivers that have errors will be indicated above the list. In that case, number of successive errors will be displayed in collector configuration form.", "Once the form validated, you can test connection and messages retrieving by using the dedicated button.", "An automatic action will do the import on configured receivers ; time between two executions can be configured in automated task form.", "Another automatic action will send notifications when any collector repetitively fails to import emails. See notifications configuration .", "Answers to emails generated from GLPI for tickets are cleaned when importing from a collector: all content between up and bottom tags will be removed. Answers must be done before or after original message." ] }, { "title": "Blacklists", "items": [ "Receivers can use a blacklist mechanism in order to remove recurrent but useless contents, like email signatures.", "Blacklist can also prevent emails to be imported from specific email addresses; this can be useful to prevent spam, or to handle emails aliases." ] }, { "title": "Rules for assigning a ticket opened via a receiver", "items": [ "GLPI implements a mechanism for routing tickets opened by email, in order to create them in the right entity. This is based on the rules engine.", "Available criteria are:", "name of receiver", "requester", "email domain, whether it is known or not", "email headers: `auto_submitted, from, in_reply_to, received, subject, to, X-Auto-Response-Suppress, X-priority, X-UCE-Status`", "email body.", "Finally, there is a third type of criteria which operates on data specific to the user or to the configuration of the entities:", "known email domain: checks that the email domain of the email sent corresponds to a domain entered in an entity. This criterion makes it possible to eliminate, for example, all spam, i.e. messages not coming from authorized domains", "user: group: checks that the GLPI user associated with the sender's e-mail address belongs to a given group;", "user with profile: the user has a given profile;", "user with single profile: the user has one and only one profile in GLPI. If the profile is associated with several different entities, then the one that is defined as the default entity in the user's personalization options will be the entity of the ticket. If none is defined in the preferences, the rule does not match", "user with the profile only once: the user has a given profile only once: it does not have the profile assigned on several separate entities.", "The actions are either the refusal of the ticket (with or without notification of the refusal to the issuer), or the import into an entity (manual, from TAG, from mail domain, from user profile).", "An example of using the engine is as follows:", "rule refusing emails whose email domain is unknown (not taking spam into account);", "rule refusing messages from mailing lists;", "rules affecting emails if the user has only one profile (case of users of the simplified interface);", "rule affecting emails to an entity if the user has a particular profile (e.g. for super administrators, who have access to all entities, but are physically in a particular entity)." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/collectors.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/collectors.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/collectors.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0038", "title": "Components", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "components" ], "relatedIssuePatterns": [ "configuration", "components" ], "summary": "The hardware components that can be added to computers are configurable.", "sections": [ { "title": "Overview", "items": [ "The hardware components that can be added to computers are configurable.", "A hardware component is defined by a type, a name, a manufacturer, a comment, and several fields specific to the type of component. For example, for a system board, you can enter the chipset.", "It is possible to fill in other component types inside the Other Components type. However, it is not possible to add other types than those listed here.", "Once a component type has been selected (Motherboard, Processor...), you are redirected to the list of components already created." ] }, { "title": "Main", "items": [ "Information that defines a hardware component (different information depending on the type of component).", "Example for a Processor:" ] }, { "title": "Items", "items": [ "The elements tab allows to visualize the computers linked to the component.", "It is possible to modify the characteristics of a component only for the linked item", "From the Elements tab of the component, click on the Update link.", "Several tabs are then proposed:", "Element - Component name link tab: lists the characteristics of this component", "Management tab : manage financial and administrative information", "Documents tab", "Locks tab", "Historical tab", "Contracts tab", "All tab : for an item, all information is displayed on a page" ] }, { "title": "Projects", "items": [ "This tab allows you to view the projects associated with the component. From this tab, you can add existing projects, but you cannot create new ones.", "To link or unlink a project, go to link or unlink a project", "To create a new project, go to manage projects" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/components.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/components.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/components.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0039", "title": "Configure automatic actions", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "crontasks" ], "relatedIssuePatterns": [ "configuration", "crontasks" ], "summary": "GLPI has multiple automatic actions (also referred to as crontasks) that are periodically scheduled jobs. These actions can be configured to run at a specific frequency and run in either GLPI or CLI mode.", "sections": [ { "title": "Overview", "items": [ "GLPI has multiple automatic actions (also referred to as crontasks) that are periodically scheduled jobs. These actions can be configured to run at a specific frequency and run in either GLPI or CLI mode.", "In GLPI mode, the actions are started occasionally when users navigate GLPI. In CLI mode, the actions are started in their own session via cron, Scheduled Tasks, or some other external task scheduler. You may configure some actions to run in GLPI mode and others to be CLI. Some actions may support only one of the modes." ] }, { "title": "Configure CLI mode", "items": [ "To run CLI mode tasks, you will need to configure your external task scheduler to call GLPI front/cron.php file periodically. It is recommended to have it run every minute to ensure that actions that are ready to run, get ran as soon as possible.", "For Linux/MacOS, you should add the following to the web server's user's (www-data, apache, etc) crontab:", "php GLPI/front/cron.php", "You will need to replace GLPI with the path to your GLPI folder. You may also need to replace php with the full path to your php binary if it is not in the PATH." ] }, { "title": "Force execution of action from CLI", "items": [ "To execute a specific action from the command-line, you can run (for mailgate action):", "php GLPI/front/cron.php --force mailgate", "You will need to replace GLPI with the path to your GLPI folder.", "Forcing the action to run will ensure it is run even if it is not scheduled to run again yet." ] }, { "title": "alertnotclosed (Ticket)", "items": [ "Send notification alerts for tickets that have been open a certain number of days without being closed. Notifications must be enabled for this action to work. The number of days can be configured for each Entity." ] }, { "title": "cartridge (CartridgeItem)", "items": [ "Send notification alerts for cartridge stock under the alert threshold. Notifications must be enabled for this action to work. The alert threshold can be changed for each Cartridge." ] }, { "title": "certificate (Certificate)", "items": [ "Send notification alerts for certificates that are about to expire. Notifications must be enabled for this action to work. The expiration warning delay can be changed for each Entity." ] }, { "title": "checkAllUpdates (Glpi\\Marketplace\\Controller)", "items": [ "Checks all installed plugins to see if there is an update available. The plugins must be available via the marketplace even if they weren't installed that way in order for the update detection to work. If you have notifications enabled, you can receive a notification regarding the available updates. Otherwise, the available updates are listed in the action's log." ] }, { "title": "checkdbreplicate (DBconnection)", "items": [ "Checks the status of all database replicates including that it is reachable from GLPI and that it is in sync with the main database. If you have notifications enabled, you can receive a notification regarding any issues with the replicates. Otherwise, the issues are listed in the action's log." ] }, { "title": "checkupdate (CronTask)", "items": [ "Checks for a new GLPI version." ] }, { "title": "circularlogs (CronTask)", "items": [ "Removes entries in logs in the files/_log folder that are older than a certain number of days which is configurable within the action form itself." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/crontasks.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/crontasks.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/crontasks.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0040", "title": "Ticket categories", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "assistance" ], "relatedIssuePatterns": [ "configuration", "assistance" ], "summary": "The list of ticket categories is tree-like: each element can have sub-elements. It can be delegated by entity.", "sections": [ { "title": "Overview", "items": [ "Assistance ++++++++++" ] }, { "title": "Overview", "items": [ "The list of ticket categories is tree-like: each element can have sub-elements. It can be delegated by entity.", "In the form of a ticket category, you can find some information about this category including but not limited to:", "Responsible and technical group for the automatic assignment of tickets", "Default category of the knowledge base when you want to add a solution of a ticket", "Visibility of the category depending on the interface (simplified/standard) or object", "Ticket template to use for this category", "Parent category", "If a template is chosen, it will be assigned to the choice of the category and will therefore override the one that would have been defined in the entity or via a business rule.", "A link with the categories of the knowledge base is possible. If a category is chosen, clicking on the ticket category help in a ticket leads directly to all the articles in the knowledge base for this category." ] }, { "title": "Ticket categories", "items": [ "Displays a list of child ticket categories and allows adding new ones." ] }, { "title": "Task categories", "items": [ "The list of task categories is tree-like: each element can have sub-elements. It can be delegated by entity.", "In the form of a task category, you can find some information about this category including but not limited to:", "Name", "Parent category" ] }, { "title": "Task categories", "items": [ "Displays a list of child task categories and allows adding new ones." ] }, { "title": "Solution types", "items": [ "This list is a list of valid flat values. It can be delegated by entity." ] }, { "title": "Request sources", "items": [ "This list is a list of valid flat values for all entities.", "It specifies if this source should be defined by default for tickets and/or collectors." ] }, { "title": "Solution templates", "items": [ "This list is a list of valid flat values. It can be delegated by entity.", "It allows to predefine the content as well as the type of a solution and can be visible or not from the sub-entity.", "Solution templates cannot be translated" ] }, { "title": "Project states", "items": [ "This list is a flat value list valid for all entities.", "It allows to define the statuses applied to a project as well as its state." ] }, { "title": "Project types", "items": [ "This list is a list of flat values valid for all entities.", "It is used to define the types applied to a project." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/assistance.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/dropdowns/assistance.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/assistance.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0041", "title": "Calendar", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "calendar" ], "relatedIssuePatterns": [ "configuration", "calendar" ], "summary": "The calendars used within GLPI are configurable by entity. They are characterized by periods of opening as well as periods of closing.", "sections": [ { "title": "Overview", "items": [ "Calendar ++++++++", "The calendars used within GLPI are configurable by entity. They are characterized by periods of opening as well as periods of closing.", "These calendars are used in the SLA (see Configure SLAs) and the configuration of entities ." ] }, { "title": "Time ranges", "items": [ "Corresponds to the opening time slots of the entity. You can add as many as necessary per day as long as these slots do not overlap." ] }, { "title": "Close times", "items": [ "Lists the closing periods assigned to this calendar and allows you to add a new one; see lca configuration of closing periods ." ] }, { "title": "Close times", "items": [ "The list of closure periods is a flat list of valid values. It can be delegated by entity.", "A closure period consists of a name, a period and whether this closure is recurring or not.", "Concerning the field Recurring, if it is in Yes it means that the period indicated is valid all the time. In this case GLPI would not care about the year indicated.", "Very useful to indicate the holidays recurring each year (Christmas, Victory of 1945, May 1 ...) or the period of closure of the company (closed every year from 1 to 31 August) and especially it avoids re-entering the same dates each year." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/calendar.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/dropdowns/calendar.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/calendar.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0042", "title": "Locations", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "general" ], "relatedIssuePatterns": [ "configuration", "general" ], "summary": "The list of locations is organized into a tree structure. Each location can have sub-locations (Location 1 > Sub-location 1 > Sub-sub-location 1). It can be delegated by entity.", "sections": [ { "title": "Overview", "items": [ "Common ++++++" ] }, { "title": "Overview", "items": [ "The list of locations is organized into a tree structure. Each location can have sub-locations (Location 1 > Sub-location 1 > Sub-sub-location 1). It can be delegated by entity.", "In the record of a location, there is some information about it including:", "The parent location", "Building number", "Room number", "GPS coordinates (longitude, latitude, altitude)", "Street address", "If you allow GLPI to use your location, the map displayed when creating a new location will automatically show your approximate location to help make assigning GPS coordinates easier." ] }, { "title": "Locations", "items": [ "Displays a list of locations that are children of the current location and gives an option to add new child locations." ] }, { "title": "Items", "items": [ "Displays a list of items that have this location assigned to them. You are able to filter this list by a specific item type (Computers, Monitors, etc)." ] }, { "title": "Sockets", "items": [ "Lists the network sockets assigned to this location and allows to add a new one. In this case, when selecting a socket on a network port of a device, only the available network sockets of the device location (and child locations) are shown. The addition can be single via the top part or multiple via the bottom part. For adding multiple sockets, you can prefix the socket number as shown in the screenshot. Another example: considering the prefix bru, 9 and 11 the socket numbers and srv the suffix; the network sockets created will be named: bru09srv, bru10srv and bru11srv." ] }, { "title": "Status of items", "items": [ "The list of statuses is organized into a tree structure. Each status can have sub-locations (Status 1 > Sub-status 1 > Sub-sub-status 1). It can be delegated by entity." ] }, { "title": "Statuses of items", "items": [ "Displays a list of statuses that are children of the current status and gives an option to add new child statuses." ] }, { "title": "Manufacturers", "items": [ "This list is a flat list of values valid for all entities.", "This dropdown type cannot be translated." ] }, { "title": "Blacklists", "items": [ "This list is a flat list of values valid for all entities.", "It includes the value you want to blacklist as well as what type to blacklist (IP, MAC, serial number, UUID or email). Blacklists are used for automatic imports via an inventory agent or by the receiver.", "This dropdown type cannot be translated." ] }, { "title": "Blacklisted email content", "items": [ "This list is a flat list of values valid for all entities.", "It allows the receiver to not import an email containing the defined text. This can allow, among other things, to fight against spam in the case of the authorization of ticket creation for anonymous emails.", "This dropdown type cannot be translated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/general.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/dropdowns/general.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/general.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0043", "title": "IP networks", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "internet" ], "relatedIssuePatterns": [ "configuration", "internet" ], "summary": "The IP protocol is represented in several forms:", "sections": [ { "title": "Overview", "items": [ "Internet Dropdowns ++++++++++++++++++", "The IP protocol is represented in several forms:", "IP addresses", "IP networks", "FQDN", "A device connects to a network through network ports .", "To a network port, one or more Network Names are associated (see below).", "A Network Name can belong to an Internet Domain. It can contain one or more IP addresses (see below) and it can have several aliases.", "An IP address belongs to an IP network (see below).", "At the IP protocol level, networks are either in IPv4 or IPv6.", "GLPI manages IPv4 and IPv6 differently. The only differences are the format of the addresses and masks.", "212.85.137.66 is an IPv4 address, while 2a00:1450:4007:803::1012 is an IPv6 address.", "GLPI considers IPv4 as a subset of IPv6 through IPv4-mapped IPv6 addresses and treats them the same.", "GLPI uses two representations for the IP addresses (IPv6 ad IPv4):", "The binary representation allows GLPI to make the analysis of the relations between networks, addresses and masks. It is inaccessible to the user.", "The textual representation is used for displaying and entering data.", "IPv4 addresses and masks are represented in their classic form (e.g., 212.85.137.66, 255.255.255.0). The representation of IPv6 addresses is the canonical notation (ie: 2001:db8:0:85a3:0:0:ac1f:8001 rather than 2001:0db8:0000:85a3:0000:0000:ac1f:8001). In this form, you may omit 1 - 3 leading zeros in each group. IPv6 masks are represented in the form of the subnetwork prefix (ie: number of bits to 1 in the mask)." ] }, { "title": "Overview", "items": [ "IP networks allows you to define the network topology. They group together a set of IP addresses grouped according to the topology defined by the network administrators' addressing plan.", "They can be nested, and the hierarchy of IP networks depends on the addresses and masks of these networks as as well as their associated identities. For example, 192.168.1.0/255.255.255.0 is a sub-network of 192.168.0.0/255.255.254.0.", "The hierarchy is managed implicitly and cannot be modified manually.", "A network is composed of at least an address and a mask. A gateway can optionally be included.", "A network is said to be addressable if it is used for internal routing of computers. In other words, its subnet mask and its gateway are used by all the equipment on the network (if one or more computers do not have the same information, this can cause routing problems...). Generally a network with a gateway is addressable because the gateway is known by all the equipment and it can only belong to one subnet. But an addressable network does not necessarily have a gateway. This is for example the case of private networks (192.168.48.0/255.255.255.0...) or the local loop (127.0.0.0/255.255.255.0 or ::1/128)." ] }, { "title": "VLAN", "items": [ "Displays a list of VLAN associated with this IP network and allows adding new ones." ] }, { "title": "IP addresses", "items": [ "Lists the IP addresses of this network.", "You can sort this list by IP number by clicking on the IP Addresses link or by type of equipment by clicking on the Sort by Item Type link. In this case, you will have a table by type of element." ] }, { "title": "Network names", "items": [ "Displays a list of network names for the domain." ] }, { "title": "Wi-Fi networks", "items": [ "TO BE DONE" ] }, { "title": "Network names", "items": [ "A network name is the unique identification of a machine from the Internet point of view.", "Generally, a device is identified by one or more particular names on the network. The DNS server will resolve this name to an IP address. In case both IPv4 and IPv6 are used, this name will return two IP addresses: one in IPv4 and the other in IPv6. This is why a network name can have several IP addresses.", "A network name is composed of a name that corresponds to the FQDN label and one or more IP addresses.", "The IP network field appears in order to retrieve information about the different IP networks available. This information is not kept in the network name because it can have several IP addresses and each can belong to several IP networks.", "When entering a network name, the validity of the name as well as that of each IP address is checked. If one of these elements is not valid then it is rejected.", "To add an IP address to a network name, click on the plus button in front of the IP address entry fields. To remove an IP address, simply delete the contents of the IP field you wish to remove." ] }, { "title": "Network alias", "items": [ "Displays a list of aliases for this network and allows adding new ones.", "Traditionally, the network name is the one used by DNS for reverse resolution of an IP address, while the aliases correspond to the CNAME of the FQDN name.", "Similarly, the alias name must have a valid FQDN label" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/internet.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/dropdowns/internet.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/internet.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0044", "title": "Types", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "others" ], "relatedIssuePatterns": [ "configuration", "others" ], "summary": "Some plugins can provide additional headings, which are configurable in the same menu.", "sections": [ { "title": "Overview", "items": [ "Others ++++++", "Some plugins can provide additional headings, which are configurable in the same menu." ] }, { "title": "Overview", "items": [ "Whatever the type, the list is a flat list of values valid for all entities.", "It allows to define the name of the tab type and can be translated." ] }, { "title": "Models", "items": [ "Whatever the model, the list is a list of flat values valid for all entities.", "It allows to define the name of the model of the tab and can be translated." ] }, { "title": "Virtual machines", "items": [ "Whatever the sub-title (models or virtualization system, state of virtual machines), the list is a flat value list valid for all entities.", "It allows you to define the name of the virtualization model or system or the name of the state of the virtual machines.", "Only the state of the virtual machines can be translated." ] }, { "title": "Document headings", "items": [ "This list is tree-like: each element can have sub-elements. It is valid for all entities.", "The Document headings tab lists the subheadings already created and allows you to add a new one." ] }, { "title": "Document types", "items": [ "This list is a flat list of values valid for all entities.", "The application offers a number of types by default, but it is possible to add more by providing the following information:", "the name of the document type", "the extension, for example: .txt or .pdf; the detection of the documents that can be added is based on this information", "the file name for the desired document icon (Place the icon files in the pics/icones directory under the GLPI installation file tree)", "the MIME type if necessary", "the authorization to download this type of file (yes or no)", "The type of document can be a regular expression. This allows for example to authorize to define a set of documents FILENAME.XXXXYYY where XXXX is a number and YYYY the date of the current fiscal year. In this case the regular expression could be /[0-9]+/ to indicate any extension composed exclusively of numbers." ] }, { "title": "Knowledge base categories", "items": [ "This list is tree-like: each element can have sub-elements, which facilitates navigation and search. It can be delegated by entity.", "In the record of a category in the knowledge base, in addition to the name of the category, there is information about the parent category (as a child of) and whether the category can be visible to sub entities.", "The Knowledge Base Categories tab lists the sub-categories already created and allows you to add a new one." ] }, { "title": "Operating systems", "items": [ "Whatever the sub-title, the list is a flat list of values valid for all entities.", "Only the update sources can be translated." ] }, { "title": "Networks", "items": [ "All lists in this part are flat value lists.", "Network interfaces, firmware and networks are valid for all entities.", "Network sockets, domains and VLANs can be delegated per entity with or without sub-entity visibility." ] }, { "title": "Software categories", "items": [ "This list is tree-like: each element can have sub-elements. The values are defined for all entities", "The Software categories tab lists the subcategories and allows you to add a new one." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/others.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/dropdowns/others.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/dropdowns/others.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0045", "title": "External links", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "external-links" ], "relatedIssuePatterns": [ "configuration", "external-links" ], "summary": "Some elements of GLPI can be associated with a set of links to external applications. These are visible from the Links tab of the various forms.", "sections": [ { "title": "Overview", "items": [ "Some elements of GLPI can be associated with a set of links to external applications. These are visible from the Links tab of the various forms." ] }, { "title": "Add an external link", "items": [ "Click on + Add", "Enter a name", "Enter an URL", "Choose your icon", "You can choose to open it in a different tab", "From a GLPI object, select the newly created link so that it appears in the Links tab." ] }, { "title": "Add an \"generic\" external link", "items": [ "You can add a generic link for all elements of a GLPI object.", "In the links tab of your objet, click on Configure XXXXXXXX links (or go to Setup > External Links)", "Click on + Add", "To setup a link, it is possible to use tags which will be replaced by the values of the element. External links now use Twig templates. Existing links will be converted automatically during the upgrade to GLPI 11, but new links need to use Twig syntax. [NAME] -> {{ NAME }}.", "The tags are :", "================= ============================================================================================== {{ LOGIN }} The logged in user's username ----------------- ---------------------------------------------------------------------------------------------- {{ ID }} The internal numeric ID for the item ----------------- ---------------------------------------------------------------------------------------------- {{ NAME }} The name of the item ----------------- ---------------------------------------------------------------------------------------------- {{ LOCATION }} The name of the item's location ----------------- ---------------------------------------------------------------------------------------------- {{ LOCATIONID }} The internal numeric ID for the item's location ----------------- ---------------------------------------------------------------------------------------------- {{ IP }} The IP address of the item ----------------- ---------------------------------------------------------------------------------------------- {{ MAC }} The MAC address of the item ----------------- -------------------------------------------------------------------------------------", "For example, the comment field would be {{ item:comment }} The field name is case sensitive and typically it will need to be all lowercase. ================= ==============================================================================================", "Each link can be associated with one or more element types.", "If the content is empty, a simple link will be generated. If content is present, it is a link to the download of the content that will be generated." ] }, { "title": "For remote access on computer", "items": [ "Create an external protocol link with the name link with the name {{ NAME }}.rdp", "Set the file content by inserting the content of an RDP type file and replacing the ip / name / domain by TAGS like {{IP}}, {{NAME}}, {{DOMAIN}}.", "(To obtain the contents of an RDP file, open it with a notepad-type tool)", "When using tags from network ports (IP, MAC), if the hardware has several, then this will create as many create as many links as there are ports. For example, for a machine with 2 different IP addresses, 2 links will be displayed." ] }, { "title": "A web type link", "items": [ "Create an external protocol link with the name https://{{IP}} and assign it to the network hardware." ] }, { "title": "Remote control through a VNC extension", "items": [ "Some VNC implementations provide an extension that allows to take control of a computer through a browser. In general, the port used is 5900. The corresponding link will be of type https://{{IP}}:5900 or https://{{NAME}}.{{DOMAIN}}:5900." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/external_links.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/external_links.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/external_links.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0046", "title": "Fields unicity", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "fields-unicity" ], "relatedIssuePatterns": [ "configuration", "fields-unicity" ], "summary": "GLPI has a mechanism to perform uniqueness checks before the creation of an object in the database.", "sections": [ { "title": "Overview", "items": [ "GLPI has a mechanism to perform uniqueness checks before the creation of an object in the database.", "This allows you to track and/or block the presence of duplicate objects based on matching certain fields. For example, you can configure a fields unicity rule for computers using the serial number field. This applies to manual additions and additions made from an external source such as an inventory tool.", "Uniqueness is defined by a name, an object type, and one or more fields. When multiple fields are specified, all of them are checked together instead of individually (Ex: serial number AND UUID match another computer. Uniqueness checks for fields only apply if the field is not empty. For example, multiple computers with a blank serial number would be allowed. Each uniqueness rule has options to refuse the addition of the object and/or send a notification if it is determined to not be unique.", "Th criteria added in the blacklists will be ignored when calculating uniqueness." ] }, { "title": "The different tabs", "items": [ "Duplicates", "The duplicates tab lists all the values corresponding to the criteria that are currently duplicated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/fields-unicity.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/fields-unicity.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/fields-unicity.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0047", "title": "API", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "api" ], "relatedIssuePatterns": [ "configuration", "api" ], "summary": "API configuration parameters and access limitations.", "sections": [ { "title": "Overview", "items": [ "API configuration parameters and access limitations.", "Here you can see/set the URL for the API. This should match your GLPI URL with /apirest.php at the end.", "There is also a link for the API documentation." ] }, { "title": "Authentication", "items": [ "There two methods of logging in to the API that can be individually enabled.", "Credentials - Allows the use of a user's login and password", "External token - Allows the use of a personal token which can be found on the user's personal page (Only visible to them)", "You can also manage the registered API clients from this tab. Each client is comprised of a name, a logging method (historical, logs, or none) and an application token at least. You may also configure an IP range to limit access to specific clients." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/api.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/api.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/api.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0048", "title": "Assets", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "assets" ], "relatedIssuePatterns": [ "configuration", "assets" ], "summary": "This tab permit to configure global parameters for inventory.", "sections": [ { "title": "Overview", "items": [ "This tab permit to configure global parameters for inventory." ] }, { "title": "Assets", "items": [ "Enable the financial and administrative information by default", "Applicable for all objects in the inventory", "Software category deleted by the dictionary rules", "It is possible to automatically change the category of software deleted by dictionary rules. By default they are automatically moved to the FUSION category.", "End of fiscal year", "Used in the Management section", "Automatic fields (marked by)", "When a template is created, it is possible to add automatically generated fields from a template. For example, the name of the asset or the inventory number. The values of these fields can be incremented either by entity or globally.", "Restrict monitor management", "Restrict device management", "Restrict phone management", "Restrict printer management", "When creating a device manually, the user is asked to choose the type of management (unitary or global). A global management only imports an element once, unlike a unitary management which imports it as many times as it is used. For example, a printer shared by several users or a monitor connected to a screen switch. Subsequently, a unitary managed equipment can be switched to global management mode. It is possible to restrict the type of management depending on the equipment." ] }, { "title": "Automatically update of the elements related to the computers", "items": [ "Interfacing with an inventory tool makes it possible to take an automated inventory of the equipment. This interfacing is possible through the native inventory feature or a plugin.", "When connecting or updating", "When connecting a device (that is unit managed) directly to a computer, it is possible to have information retrieved from the computer assigned to it such as the User.", "When disconnecting", "When disconnecting a device (that is unit managed) from a computer, it is possible to remove some of the data in the Computer such as the User.", "For example, When the inventory is first retrieved, you can define that the monitor connected to the computer will have the status \"Production\". Then, when disconnected, it will take the status \"Available\"." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/assets.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/assets.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/assets.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0049", "title": "Assistance", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "assistance" ], "relatedIssuePatterns": [ "configuration", "assistance" ], "summary": "This tab allows management of GLPI assistance part.", "sections": [ { "title": "Overview", "items": [ "This tab allows management of GLPI assistance part." ] }, { "title": "Assistance", "items": [ "image", "Step for the hours (minutes)", "Amount of minutes between each step for minutes under an hour in duration dropdowns. Example: 5 minutes shows 5, 10, 15, 20, ..., 55, 60.", "Default file size limit imported by the mails receiver", "Maximum size of files to allow to import by the receiver. This should be adjusted along with the maximum file size option on the management tab and the max_upload_size PHP directive.", "Default heading when adding a document to a ticket", "Allows you to set a default classification for documents uploaded to a ticket.", "Keep tickets when purging hardware in the inventory", "If enabled, the tickets related to an asset being purged will remain. Otherwise, they are purged along with the asset.", "Allow anonymous ticket creation (receiver)", "Anonymous ticket creation is disabled by default. Activating the option is necessary when using an email collector to allow the creation of tickets by users not recognized by GLPI.", "Limit of the schedules for planning", "Time range displayed in the planning screen.", "By default, a software may be linked to a ticket", "Allow associating a software with a ticket by default.", "Show personal information in new ticket form (simplified information)", "Display the name, phone number, and location of the user. If needed, the Edit button redirects to the main tab of the user's preferences.", "Allow anonymous followups (receiver)", "Allows a user not present in GLPI to respond to an email from GLPI." ] }, { "title": "Matrix of calculus for priority", "items": [ "|image| The priority definition matrix allows you to define the priority of tickets according to the level of impact and urgency. The availability of these levels in the application can also be defined but the Medium level cannot be deleted." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/assistance.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/assistance.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/assistance.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0050", "title": "Default values", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "default-values" ], "relatedIssuePatterns": [ "configuration", "default-values" ], "summary": "This tabs allows to configure the display preferences that are used by default. They can be overridden for each user (see manage preferences ).", "sections": [ { "title": "Overview", "items": [ "This tabs allows to configure the display preferences that are used by default. They can be overridden for each user (see manage preferences )." ] }, { "title": "Personalization", "items": [ "Default language", "The language to use in the GLPI interface", "Results to display by page", "The number of results displayed in the search results list. If a user sets this higher than what is specified in the general setup, then they will be limited to the general setup's value.", "Display the complete name in tree dropdowns", "Display the full name of child items in a tree dropdown", "Show GLPI ID", "Adds the GLPI ID after its name on the item's edit form", "Notifications for my changes", "Receive notifications for the actions that the logged in user has done. This does not apply to the creation of a ticket for which the notification is systematically sent (proof of creation).", "PDF export font", "The font used when generating PDF exports", "Go to created item after creation", "If enabled, the user would be redirected to the edit from of the item after it gets created. Otherwise, they would remain on the new item form to be able to add more items.", "Date format", "Display format for dates", "Number format", "Display format for numbers", "Display order of surnames/firstnames", "Display order for a user's first and last name", "Display counters", "If enabled, the number of elements will be shown next to some tab names such as the Items tab in a Ticket.", "CSV delimiter", "Character to delimit fields in a CSV export", "Results to display on home page", "The number of items to display in the Ticket, Change, and Problem tables on the home page. If this parameter is set to 0, only the table titles will be displayed but you can access their respective contents by clicking on the name of the table.", "Keep devices when purging an item :", "If enabled, the components linked to an item that is being deleted can be preserved. Otherwise, they will be deleted along with the item." ] }, { "title": "Assistance", "items": [ "Private followups by default", "If enabled, followups are pre-selected to be private.", "Private tasks by default", "If enabled, tasks are pre-selected to be private.", "Tasks state by default", "Pre-selected state for tasks", "Pre-select me as a technician when creating a ticket", "The logged in user will automatically be assigned to the ticket while creating it. This only applies to users who can be assigned to tickets.", "Priority colors", "Define the colors used in the interface to differentiate the different priority levels.", "Show new tickets on the home page", "If the logged in user has the right to see all tickets, a table listing all tickets with the \"New\" will be displayed in the Overview tab of the home page.", "Request sources by default", "Pre-selected request source for new tickets", "Automatically refresh data (tickets list, project kanban) in minutes :", "Automatically refresh the information in the tickets list and Kanban. If set to 0, the automatic refresh is disabled." ] }, { "title": "Due date progression", "items": [ "Allows to define the colors that will be applied in the progress bar of an object. These different states depend on the thresholds set in percent, hours or days." ] }, { "title": "Dashboards", "items": [ "Configure the default dashboards for the home page (central), assistance module, assets module, and above the tickets search results list." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/default_values.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/default_values.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/default_values.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0051", "title": "General configuration", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "general-configuration" ], "relatedIssuePatterns": [ "configuration", "general-configuration" ], "summary": "This tab permits to customize main application appearance.", "sections": [ { "title": "Overview", "items": [ "This tab permits to customize main application appearance." ] }, { "title": "Description of fields", "items": [ "URL of the application: used in different links provided in the application, in notifications, and for the API.", "Its defined at install time depending on the URL that has been used for it.", "Text in the login box: specific text to be displayed at the top of the login block", "Allow FAQ anonymous access: allows Frequently Asked Question access without any login in GLPI. A link to access the FAQ will be displayed below the login box when enabled.", "Default search results limit: maximum number of search results displayed at once on all search pages", "Default characters limit: maximum number of displayed characters visible in search results. If you display a ticket content for example, it will be truncated on this number of characters", "Default url length limit: same as the above, but applying on URLs", "Default decimals limit: number of decimals displayed for amounts", "Translation of dropdowns: allows dropdowns do be translated. Once this parameter enabled, a translation tab will be added on dropdown forms (see dropdowns translations )", "Translation of reminders: same as the above, but applying on reminders", "Knowledge base translation: same as the above, but applying on knowledge base entries", "Simplified interface help link: link to help displayed for users using simplified interface", "Standard interface help link: link to help displayed for users using standard interface", "Page size for dropdown: number of elements displayed in a dropdown on each scroll", "Don't show search engine in dropdowns if the number of items is less than: search in dropdown won't be displayed if there are less results than configured here", "Items seen", "Global search: enable global search adding a search field at the top of the interface" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/general_configuration.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/general_configuration.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/general_configuration.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0052", "title": "Management", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "management" ], "relatedIssuePatterns": [ "configuration", "management" ], "summary": "The only configuration parameter available on this page is the size limit for uploaded documents.", "sections": [ { "title": "Overview", "items": [ "The only configuration parameter available on this page is the size limit for uploaded documents.", "If the upload_max_filesize PHP directive is lower than what is set here, then upload_max_filesize will be the limiting factor. You may also need to ensure the post_max_size directive is set at least a little above upload_max_filesize." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/management.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/management.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/management.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0053", "title": "Performances", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "performances" ], "relatedIssuePatterns": [ "configuration", "performances" ], "summary": "Displays information related to the different caching systems used by GLPI including:", "sections": [ { "title": "Overview", "items": [ "Displays information related to the different caching systems used by GLPI including:", "PHP opcode cache - Improves performance of the PHP engine when interpreting the different PHP files.", "User data cache - General-purpose cache used by GLPI.", "Translation cache - Cache used for translations to avoid having to read the locale files for all translations.", "You also have the ability to clear the different caches from here.", "The cache systems for user data and translations can be changed or configured from the cache:configure CLI command." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/performances.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/performances.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/performances.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0054", "title": "Security", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "security" ], "relatedIssuePatterns": [ "configuration", "security" ], "summary": "Security related parameters such as the password security policy and password expiration policy.", "sections": [ { "title": "Overview", "items": [ "Security related parameters such as the password security policy and password expiration policy." ] }, { "title": "Password security policy", "items": [ "The following options can be configured as part of the password security policy:", "Password security policy validation - The security policy is only enforced if this is enabled", "Password minimum length", "Password need digit", "Password need uppercase character", "Password need lowercase character", "Password need symbol" ] }, { "title": "Password expiration policy", "items": [ "The following options can be configured as part of the password expiration policy:", "Password expiration delay (in days) - Can be set to never to disable password expiration", "Password expiration notice time (in days)", "Delay before account deactivation (in days)" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/security.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/security.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/security.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0055", "title": "SQL replicas", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "sql-replicas" ], "relatedIssuePatterns": [ "configuration", "sql-replicas" ], "summary": "GLPI can be configured to use replica databases in some cases to improve performance.", "sections": [ { "title": "Overview", "items": [ "GLPI can be configured to use replica databases in some cases to improve performance.", "This tab is only visible if the option has been enabled in the system tab .", "To activate the replica management, you just have to fill in the connection parameters. It is advisable to use a login that has only read privileges on the database.", "You can use several replicates by separating them with a blank space. As the result in the config_db_slave.php file, the `dbhost` parameter will be an array.", "A specific port can also be added.", "If you use multiple replicas, the settings will apply to them all.", "The SQL replicas will be used in at least the following cases:", "The main server cannot be reached.", "In this case, GLPI will switch to read-only mode.", "Running reports to reduce the load on the main server.", "It is also possible to use replicas for the search engine depending on the option chosen.", "Never", "If synced (all changes)", "GLPI will check the synchronization and use the replica if all changes have been replicated.", "If synced (current user changes)", "GLPI will check the synchronization and use the replica if all the changes for the current user have been replicated. If using a read-only account, the replica will always be used.", "If synced or read-only account", "GLPI will check the synchronization and use the replica if all changes have been replicated. If using a read-only account, the replica will always be used.", "Always", "When always using the replica, it is possible that the results will be out of date. A different option should be considered before this one.", "The replication configuration of your database is not set by GLPI. You still need to configure that with the appropriate tools for your database management system." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/sql_replicas.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/sql_replicas.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/sql_replicas.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0056", "title": "System", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "system" ], "relatedIssuePatterns": [ "configuration", "system" ], "summary": "This tab allows you to view a summary of information about the web server, configure the proxy information, and to define the logging information to be recorded.", "sections": [ { "title": "Overview", "items": [ "This tab allows you to view a summary of information about the web server, configure the proxy information, and to define the logging information to be recorded.", "Logging level", "Each internal event of the application is recorded in the logs which are visible in `Administration > Logs <../../administration/logs.html>`_.", "Logs in files (SQL, email, automatic action...) :", "It is possible to record certain additional events (SQL, notifications, automatic action...) in files. These files are then available in the files/\\_log directory.", "Maximum number of automatic actions (run by CLI)", "When configuring automatic actions, it is possible to determine that they will be executed by a system external to GLPI (CLI). By default, it executes these actions one by one. It possible to increase the number of executions launched simultaneously.", "SQL replica", "Enable to usage of one or more replica databases. The replicas can be further configured in the SQL replicas tab after this option is enabled.", "A maintenance mode can be activated to allow a technical operation such as an update for example. A maintenance message is configurable and would show on the login page. In maintenance mode, you can still access GLPI via `index.php?skipMaintenance=1`.", "In the case GLPI sits behind a proxy, it is necessary to indicate the information to allow GLPI to access the Internet. This affects the checking of new versions, fetching RSS feeds, etc.", "The following screen lists all the information of GLPI necessary to report a malfunction to the GLPI development team. It is preferred to click the Copy system information button which will add a rich-text version of the system information tables to your clipboard. This format shows up in a cleaner format on GitHub than if you copy it directly." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/system.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/general/system.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/general/system.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0057", "title": "Alarm options", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "alarm-options" ], "relatedIssuePatterns": [ "configuration", "alarm-options" ], "summary": "At the entity level, you can configure the alarm options (cartridge/consumable stock alarms, expiration alarms, etc). By default, these options will inherit the value from their parent entity.", "sections": [ { "title": "Overview", "items": [ "At the entity level, you can configure the alarm options (cartridge/consumable stock alarms, expiration alarms, etc). By default, these options will inherit the value from their parent entity.", "As of GLPI 10.0, the following alarm options are available:", "Cartridges > Reminders frequency for alarms on cartridges", "Cartridges > Default threshold for cartridges count", "Consumables > Reminders frequency for alarms on consumables", "Consumables > Default threshold for consumables count", "Contract > Alarms on contracts", "Contract > Default value", "Contract > Send contract alarms before", "Financial and administrative information > Alarms on financial and administrative information", "Financial and administrative information > Default value", "Financial and administrative information > Send financial and administrative information alarms before", "Licenses > Alarms on expired licenses", "Licenses > Send license alarms before", "Certificates > Alarms on expired certificates", "Certificates > Send certificates alarms before", "Reservations > Alerts on reservations", "Tickets > Alerts on tickets which are not solved since", "Domains > Alarms on domains expiries", "Domains > Domains closes expiries", "Domains > Domains expired" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/alarm_options.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/notifications/alarm_options.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/alarm_options.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0058", "title": "Notification Definitions", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "definitions" ], "relatedIssuePatterns": [ "configuration", "definitions" ], "summary": "A notification definition in GLPI is composed of:", "sections": [ { "title": "Overview", "items": [ "A notification definition in GLPI is composed of:", "One or more notification templates", "Templates are added for specific notifications modes. This allows you to use one template for email notifications and another for browser notifications.", "A set of recipients", "The list of recipients could include specific users, groups, etc or can include dynamic recipients such as \"Requester\" which would be replaced by all user's listed as requester on a Ticket for example.", "An item type (Ex: Ticket).", "An event from the specified item type (Ex: Add)." ] }, { "title": "The different tabs", "items": [ "Notification", "A notification is composed of a certain number of specific fields to fill in:", "Name: Name of the notification.", "Active: Allows you to temporarily deactivate a notification.", "Type: Type of GLPI object to which the notification refers.", "Notification mode The notification method (Email and Browser available by default).", "Event: Indicates what will be the triggering event following the type of the object.", "Notification templates: Indicates the notification that will be sent for the object type and the event defined previously.", "Recipients", "This is where you define who will receive the notification.", "A certain number of actors of the application are proposed and the list The list varies according to the type of object defined.", "This list includes, but is not limited to:", "Administrator: person whose email address has been defined in the global configuration of email follow-ups .", "Entity Administrator: person, for each entity, whose email address is defined in the entity configuration of email follow-ups .", "Requester: The person who is listed as the requester in the ticket.", "Technician in charge of the ticket: Users assigned to the ticket.", "Group XXX: All the people who have access in the entity and who are part of the group.", "Group XXX without supervisor: All members of the group except the person declared Manager of the group.", "Group in charge of the ticket: All the members of the group to which the ticket is assigned.", "Group in charge of the ticket without supervisor: All members of the group assigned to the ticket, except for the person declared Manager of the group.", "Requesting group: All members of the group indicated as the requesting group of the ticket.", "Observer group: All members of the group indicated as the observer group of the ticket.", "Observer: The person who is the observer of the ticket.", "Profile XXX : All the people who have access in the entity and who have this profile.", "Writer: person who enters the information.", "Technical manager: The person designated as the user responsible for the asset(s) related to the ticket." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/definitions.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/notifications/definitions.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/definitions.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0059", "title": "Email follow-ups configuration", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "email-notifications" ], "relatedIssuePatterns": [ "configuration", "email-notifications" ], "summary": "For GLPI to be able to send notification via email, an email server connection will need configured.", "sections": [ { "title": "Overview", "items": [ "For GLPI to be able to send notification via email, an email server connection will need configured.", "The email server configuration can be configured globally, and then some options can be overridden at the entity level.", "Global settings can be accessed from the \"Email followups configuration\" option on the Setup > Notifications page." ] }, { "title": "Global Configuration", "items": [ "The global configuration allows you to set the following options:", "+------------------------------------------------------+------------------------------------------------------------------------------------------------+ | Option | Meaning | +------------------------------------------------------+------------------------------------------------------------------------------------------------+ | Administrator email | | GLPI Administrator email. | | | | This can be used as a special recipient in notifications | +------------------------------------------------------+------------------------------------------------------------------------------------------------+ | Administrator name | The display name to use for the Administrator email address. | +------------------------------------------------------+------------------------------------------------------------------------------------------------+ | From email | The email address to use in the From field for emails sent by GLPI. | +------------------------------------------------------+------------------------------------------------------------------------------------------------+ | From name | | The display name to use for the From email address. | | | | This name will be seen by end users. | +---", "You can test the sending of notifications from the global notification configuration form by trying to send an email to the specified Administrator email address." ] }, { "title": "Email Method - PHP", "items": [ "This option cannot be configured within GLPI and must be done in your PHP configuration. This option uses the mail() function of PHP.", "The PHP email method is blocked by most hosting providers." ] }, { "title": "Email Method - SMTP", "items": [ "The following configuration options are available for the SMTP email method(s):", "Check certificate - Verify the email server has a valid certificate.", "SMTP host - The SMTP server address.", "Port - The port to communicate with the SMTP host over.", "| Typically, this is port 25. Check your provider's documentation for more info. | Also, additional configuration may be needed if your provider needs IMAP OAuth .", "SMTP login (optional) - Username to authenticate with the email server.", "SMTP password (optional) - Password to authenticate with the email server.", "Email sender - This may be needed for some email providers.", "If this is not specified, the Administrator email will be used." ] }, { "title": "Email Method - SMTP+SSL", "items": [ "The configuration options are the same as the SMTP option but GLPI will use SSL security for the connection." ] }, { "title": "Email Method - SMTP+TLS", "items": [ "The configuration options are the same as the SMTP option but GLPI will use TLS security for the connection." ] }, { "title": "Entity Configuration", "items": [ "The following options can be overridden at an entity level (see global configuration for more information about each option):", "Administrator email", "Administrator name", "Reply-to address", "Reply-to name", "Email signature", "The entity level options can be accessed for the Notifications tab in the entity's form.", "The following options can only be configured at the entity level:", "Prefix for notifications - Text to prefix to the subject of email notifications.", "Delay to send email notifications - Optional delay to the initial sending of notifications.", "Enable notifications by default - If enabled, a user is automatically set to receive notifications in some cases such as when they are assigned to a ticket.", "Fields that are no set, will be inherited from their parent entity by default.", "<br>" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/email_notifications.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/notifications/email_notifications.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/email_notifications.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0060", "title": "Template example", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "template-example" ], "relatedIssuePatterns": [ "configuration", "template-example" ], "summary": "In this example, we will create a template for ticket mail notifications.", "sections": [ { "title": "Overview", "items": [ "In this example, we will create a template for ticket mail notifications.", "In the end, this template can be used for several ticket events:", "New ticket", "Add followup", "Add task", "Resolve ticket", "..." ] }, { "title": "Create template", "items": [ "Go to Setup > Notifications > Notification templates", "Click on Add button", "Fill in fields", "Name: `Generic tickets with timeline` for example", "Type: `Ticket`", "Comments: `Generic template for tickets, using timeline` for example", "CSS: leave empty for now", "Save to be redirected to the template translation" ] }, { "title": "Basic data", "items": [ "We are now in the editing mode of a template translation.", "Language: `Default translation` The minimum required. We will see later how to add other languages.", "Subject: `##ticket.action##: ##ticket.title##` \"[GLPI <ticket_number>]\" will be automatically added to the email subject", "`##ticket.action##`: action that triggered the notification", "`##ticket.title##`: ticket title", "Email text body: leave empty to be filled automatically", "Email HTML body: this is the field that we will mainly modify in the next chapters" ] }, { "title": "Case: New ticket", "items": [ "Let's start by adding some basic data. You can add more by using the \"Show list of available tags\" button to display the available tags.", "Email HTML body:", "##ticket.action##: ##ticket.title## ##lang.ticket.status##: ##ticket.status## ##lang.ticket.url##: ##ticket.url##", "##lang.ticket.description##: ##ticket.authors## - ##ticket.creationdate## ##ticket.description##", "`##lang.ticket.status##`: text \"Status\" automatically translated into the recipient's language", "`##ticket.status##`: ticket status", "`##lang.ticket.url##`: text \"URL\" automatically translated", "`##ticket.url##`: ticket url", "`##lang.ticket.description##`: text \"Ticket Description\" automatically translated", "`##ticket.authors##`: ticket requesters separated by ',' if there is more than one", "`##ticket.creationdate##`: ticket creation date", "`##ticket.description##`: ticket description text" ] }, { "title": "Case: Add followup, Add task, Resolve ticket", "items": [ "Follow-ups, tasks and solutions are elements of a ticket's timeline, so we'll loop through \"timelineitems\" using `FOREACHtimelineitems`.", "Email HTML body:", "##ticket.action##: ##ticket.title## ##lang.ticket.status##: ##ticket.status## ##lang.ticket.url##: ##ticket.url##", "##FOREACHtimelineitems## ##timelineitems.author## - ##timelineitems.date## ##timelineitems.description## ##ENDFOREACHtimelineitems##", "##lang.ticket.description##: ##ticket.authors## - ##ticket.creationdate## ##ticket.description##", "`##FOREACHtimelineitems##`: loop over all timeline items", "`##timelineitems.author##`: author of the timeline item", "`##timelineitems.date##`: date of the timeline item", "`##timelineitems.description##`: description text of the timeline item", "`##ENDFOREACHtimelineitems##`: end of the loop" ] }, { "title": "Layout", "items": [ "For now, we have only retrieved tags but there is no formatting yet." ] }, { "title": "Put in bold", "items": [ "Select text : e.g. `##ticket.authors##`", "Click on Bold button" ] }, { "title": "Clickable link", "items": [ "Select URL text : e.g. `##ticket.url##`", "On right-click menu, click on Link...", "Fill in the field URL = `##ticket.title##`", "You can leave the other fields unchanged and Save" ] }, { "title": "Add headings", "items": [ "Select text : e.g. `##ticket.action##: ##ticket.title##`", "Click on the format drop-down list and select Headings > Headings 1" ] }, { "title": "Add a logo", "items": [ "Without selecting any text, click on the place where you want to put your image", "Click on Insert image button", "Browse to add your image", "If necessary, you can resize via right-click menu > Image..." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/template_example.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/notifications/template_example.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/template_example.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0061", "title": "Notification templates", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "templates" ], "relatedIssuePatterns": [ "configuration", "templates" ], "summary": "A template is a global object of GLPI that defines the information included in a notification and the formatting of the information.", "sections": [ { "title": "Overview", "items": [ "A template is a global object of GLPI that defines the information included in a notification and the formatting of the information.", "The creation of a template is a complex operation, which impacts the users. Therefore, templates can only be modified by Administrators with the Update permission for the Config right. Moreover, a template is not linked to an entity, which means that it is not possible to delegate its management to an administrator of a sub-entity.", "A template reflects a communication to a user and can be available in several languages thanks to a translation mechanism. The use of tags (i.e. markers that are independent of the language used) makes it possible to create a generic translation, available for all the languages of GLPI.", "GLPI comes with a set of pre-defined templates for all notifications (tickets, reservations, financial information, cartridges, consumables, licenses, MySQL synchronization...)." ] }, { "title": "Notification template", "items": [ "First tab.", "Name: Template name", "Type: Type of GLPI object to which the template relates", "Comments: (optional) Additional information", "CSS: (optional) Style sheet used for the template in HTML", "Templates are global, they are not defined at the entity level, as notifications." ] }, { "title": "Template translation", "items": [ "Tab that lists the different notifications defined by language and allows adding a new language.", "Language: Indicates the language to which this translation refers. If no language is selected in the drop-down list, this translation will be the default for this template.", "Subject: Subject of the mail.", "Email text body: Plain text without layout, used in cases where HTML is not allowed. If the field is empty, then it is generated from the HTML body text.", "Email HTML body: Text with HTML layout.", "A default translation is applicable to all GLPI languages that do not have their own translation." ] }, { "title": "Tags", "items": [ "The tags allow to display data of the notification trigger object. e.g.: in a ticket you can retrieve its title, description, actors...", "A tag is identified by ## at the beginning and at the end.", "There are several types of tags:", "Simple: ##<object>.<field>## for the field value of a GLPI object", "Label: ##lang.<object>.<field>## for the translated label of the object's field", "Condition: to test if a field has:", "a value: ##IF<object>.<field>##` ... `##ENDIF<object>.<field>##", "a value = <V>: ##IF<object>.<field>=<V>##` ... `##ENDIF<object>.<field>##", "Loop: to display sub-objects:", "all <objects>: ##FOREACH<objects>##` ... `##ENDFOREACH<objects>##", "first <N> <objects>: ##FOREACH FIRST <N> <objects>##` ... `##ENDFOREACH<objects>##", "last <N> <objects>: ##FOREACH LAST <N> <objects>##` ... `##ENDFOREACH<objects>##" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/templates.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/notifications/templates.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/notifications/templates.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0062", "title": "Install and update plugins", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "plugins" ], "relatedIssuePatterns": [ "configuration", "plugins" ], "summary": "Adding and maintaining extensions (plugins) in GLPI.", "sections": [ { "title": "Overview", "items": [ "Adding and maintaining extensions (plugins) in GLPI.", "The first time you go to the plugins page under `Setup > Plugins`, you will be asked if you want to use the marketplace UI by default or the older plugin list. Regardless of your choice, you can always switch UIs by clicking the \"Marketplace\" and \"Plugins\" buttons at the top of the page. You may install plugins using both methods. If a plugin is install through the marketplace and manually for some reason, the version installed through the marketplace will be used." ] }, { "title": "Using the plugin marketplace", "items": [ "To use the marketplace, you will need a GLPI Network registration key. If you are not paying for a GLPI Network subscription, you can still get a free key from `<https://services.glpi-network.com>_. After you get the key, you may enter it under Setup > General on the GLPI Network` tab." ] }, { "title": "Finding plugins", "items": [ "In the plugin marketplace UI, click on the Discovery tab to view the list of all plugins offered through the marketplace. These include official plugins (free and subscription) and community plugins. On the left, you can select a category to filter plugins and use the search bar to further limit the results.", "Any plugin that has a GLPI NETWORK requires a non-free subscription. These plugins will also indicate the tier required such as BASIC, STANDARDor ADVANCED. Each paid tier includes the plugins from the lower tiers." ] }, { "title": "Installing plugins", "items": [ "On the right side of each plugin, you should see a button to install it or one or more errors explaining why it cannot be installed. When you find a plugin available to install, you can click the install button to automatically download the latest version available for your GLPI version and install it.", "Plugins installed via the marketplace are stored in the marketplace folder in the root of your GLPI instance.", "After installation, the install button will change to an enable toggle. You will need to click that button to enable the plugin after installation.", "You can click on the spanner icon to access this configuration. This plugin will also appear in the corresponding module (support, management, tools, administration, setup)." ] }, { "title": "Updating plugins", "items": [ "In the marketplace UI on the Installed tab, you can see all the plugins currently installed.", "Similar to installing plugins, there will be an update button showing if an update is available or one or more errors if there is some issue preventing an update. Like with installing plugin, you will need to re-enable the plugins after an update." ] }, { "title": "Manually managing plugins", "items": [ "The main way to discover new plugins is through the plugin catalog . Each plugin should have a download link that will take you to a GitHub page, the GLPI Network Services website (if it is a subscription-only plugin), or some other page that offers the downloads.", "After you download the plugin, you will need to extract it to the plugins folder in your GLPI directory. The new folder inside plugins should be the \"internal\" name of the plugin. This is an all lowercase identifier containing no spaces. Inside that folder should be at least two files named hook.php and setup.php.", "Once the plugin is in the plugins folder, it will be automatically detected by GLPI and will show up in your plugin list.", "All plugins listed will have a group of actions along the right side (or a message indicating why they cannot be installed or updated). After installing or updating a plugin, you will need to re-enable it." ] }, { "title": "Uninstalling plugins", "items": [ "When you uninstall a plugin using the uninstall button in the plugin list or in the marketplace UI, it does not remove the plugin code and the plugin will still show in the list of plugins to re-install.", "To permanently remove the plugin, it is necessary to delete the plugin's folder. After removing the plugin's folder there should be a new \"cleanup\" action available for the plugin in GLPI. This will remove the reference to the plugin from the database." ] }, { "title": "Plugins and Update GLPI", "items": [ "When GLPI is updated, the plugins execution is suspended. This allows you to preserve the state of a plugin before the GLPI update and restore it to its previous state once the update is complete. The plugins execution will be automatically resumed when the update corresponds to a bugfix update only (e.g. 11.0.x to 11.0.y), but this will have to be done manually in case of a major or intermediate update (11.0.x to 11.1.y or 12.0.z). This avoids having to activate the plugins one by one and avoid activating a plugin that was not activated.", "If GLPI behaves abnormally, you can also use this option to suspend all plugins and and check that the anomaly is not due to a plugin you have installed.", "To suspend your plugins, click on `Suspend execution of all plugins`:", "To reactivate the status of plugins before suspension click on `Resume execution of all active plugins`:" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/plugins.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/plugins.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/plugins.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0063", "title": "Service Levels", "category": "configuration", "tags": [ "glpi", "documentation", "configuration", "service-levels" ], "relatedIssuePatterns": [ "configuration", "service-levels" ], "summary": "There are two types of service level agreements that can be tracked in GLPI.", "sections": [ { "title": "Overview", "items": [ "There are two types of service level agreements that can be tracked in GLPI.", "Service Level Agreement (SLA): Agreement between an IT provider and the customer", "Operation Level Agreement (OLA): Agreement between groups/departments of the IT provider", "Both of these types of agreements are used in GLPI to optionally track:", "The maximum amount of time that should pass before a ticket has a technician assigned", "The maximum amount of time that should pass before a ticket is resolved", "A calendar can be associated with an SLA/OLA (see calendars ). By default, no calendar is associated and calculations are done on a working basis 7 days a week and 24 hours a day. It is also possible to use the calendar associated with the ticket (i.e. the one of the entity to which the ticket is attached).", "If the maximum resolution time is expressed in days, all the calculations will be done in days (D+1, D+4 for example) taking into account the calendar to determine the working days. In the use of the End of the working day indicator, the due date will correspond to the end of the corresponding working day. If the maximum resolution time is expressed in hours or minutes, then the calculations will be made taking into account the opening hours.", "For example, for an SLA in H+4 with a calendar defining opening hours from 8am to 6pm, a ticket opened at 4pm will have a due date of 10am the next day.", "Changing the ticket to pending status puts the SLA in sleep mode. If the ticket remains pending for 3 hours for example, the due date will be postponed by 3 hours." ] }, { "title": "Automatic assignment of service levels", "items": [ "You can automatically assign an SLA or OLA to tickets through the ticket rules engine . The association of the SLA with the ticket allows the automatic calculation of its the expiration date. Several SLA/OLAs can thus be defined and assigned according to precise criteria.", "For example, SLA 1 will be assigned if the ticket is associated to a specific category and SLA 2 for the other categories.", "If an SLA/OLA is assigned manually when the ticket is opened (by the user or via a ticket template), the business rules cannot redefine it.", "When it is assigned, it will be completely replayed and the actions associated with the escalation levels will be executed." ] }, { "title": "Escalation levels", "items": [ "After adding an SLA/OLA to a service level, you can click on the name of the SLA/OLA in the related tab of the service level to configure it more including escalation levels.", "After adding an escalation level to an SLA/OLA you can click its name to configure the criteria to trigger it and the actions to take after it is triggered.", "Each level triggers automatic actions to resolve the ticket as soon as possible. A level is triggered before or after the expiration date of the SLA/OLA according to the defined delay.", "For example, one day before the deadline, the ticket is assigned to level 2 support and its priority is changed to High.", "Escalation levels can be conditioned by trigger criteria. Without criteria, the level will be triggered but if criteria are criteria are defined, they will be checked before applying the escalation level.", "For example, if 1 day before the due date you want to send a reminder to the administrator if the ticket is still in New status, you need to set the criteria as Status is New." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/service_levels.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/configuration/service_levels.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/configuration/service_levels.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0064", "title": "Manage knowledge base", "category": "tools", "tags": [ "glpi", "documentation", "tools", "knowledgebase" ], "relatedIssuePatterns": [ "tools", "knowledgebase" ], "summary": "GLPI knowledge base has two main targets:", "sections": [ { "title": "Overview", "items": [ "GLPI knowledge base has two main targets:", "Gather internal knowledge for technicians;", "Provide information as a public FAQ to enable users to solve simple problems on their own.", "Only public FAQ items are visible to users of simplified interface. Other elements are visible only to technicians via standard interface.", "Each article of the knowledge base must have one or more targets, being entities, groups, profiles or users, to be readable. As long as an article has no target, it is visible only by its writer, is flagged as unpublished and appears in table Unpublished articles on the home page of the knowledge base.", "Targeting applies in the same way whether the article is in the FAQ or only in the knowledge base.", "You can publish an article for everyone by targeting the root entity.", "By default, articles are not translatable. However, this functionality can be activated, see general configuration .", "It is possible to attach documents to articles of the knowledge base.", "An article can be made visible during a time slot by defining a start date and an end date.", "Elements which should not be interpreted when displayed can be defined with pre-formated style (<pre>` in HTML). Tags like `<VirtualHost>` can therefore be inserted and will be displayed. Other HTML tags (`<TAG>...</TAG> may disappear when editing; to have complete visibility of the text, it is possible to switch to HTML mode where all elements will be visible. The browser may also modify dynamically content (case change, tags adding) when editing.", "It is possible to create categories and sub-categories in order to organize browsing (see Configure drop-downs ). User can then use several tabs to search and browse knowledge base:", "Search", "This tab is the default tab, displaying recent articles, popular articles and last changes. It allows also to search inside knowledge base.", "Browse", "This tab allows to browse tree structure of categories.", "Manage", "This tab is only visible for knowledge base administrators. Depending on user's permissions, it is possible to access quickly user's articles, user's unpublished articles, all unpublished articles...", "The knowledge base search engine provides operators for complex search: + - ~ < > ” ” ().", "`+`: word must be there;", "`-`: word must not be there;", ": truncate suffix;", "`\" \"`: contained sequence must be searched literally;", "< >: define order on search elements;", "`()`: group when using < and >.", "Examples :", "printer failure", "-> Search lines containing at least one of these words", "+printer +failure", "-> Search lines containing both words", "+mail thunderbird", "-> Search lines containing word mail but rank higher lines containing also word thunderbird", "+mail -outlook", "-> Search lines containing word mail but not word outlook", "+mail +(>thunderbird <outlook)", "-> Search lines containing word mail and thunderbird, or mail and outlook, in any order, but rank mail thunderbird higher than mail outlook", "open", "-> Search lines containing words such as openoffice, openwriter, openbar, openphp...", "\"openoffice suite\"", "-> Search lines containing exactly sentence openoffice suite" ] }, { "title": "Knowledge base", "items": [ "This tab displays a table with article category, subject, content, writer, creation date, last modification date, number of views and FAQ membership.", "If an article is unpublished (i.e. has no target), this information will appear in red above number of views." ] }, { "title": "Target", "items": [ "This tab allows to manage article's targets.", "An article is by default personal and therefore only visible by its creator.", "For an article to become visible by other users, targets must be added to it, a target being either an entity, a group, a profile or a user who will be able to consult the article." ] }, { "title": "Edit", "items": [ "This tab allows, if appropriate permission, to modify or delete an article." ] }, { "title": "Revision", "items": [ "This tab allows to consult all article revisions: each saved modification of the article will create a revision storing the previous version of the article.", "Revisions can be shown and restored." ] }, { "title": "Comments", "items": [ "This tab allows platform's users to add their comments and discuss the article." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/knowledgebase.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/tools/knowledgebase.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/knowledgebase.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0065", "title": "Manage projects", "category": "tools", "tags": [ "glpi", "documentation", "tools", "projects" ], "relatedIssuePatterns": [ "tools", "projects" ], "summary": "Project management in GLPI allows to follow entirely a project's progress by creating tasks and building teams; projects can be optionally linked to a change .", "sections": [ { "title": "Overview", "items": [ "Project management in GLPI allows to follow entirely a project's progress by creating tasks and building teams; projects can be optionally linked to a change .", "A GLPI project allows:", "defining tasks associated to the project and following their progress;", "creating teams for a project and its tasks;", "triggering sub-projects inside the project;", "building GANTT diagrams;", "using Kanban method;", "attaching costs;", "linking to GLPI ITIL items.", "A project can be hierarchical, a project can therefore have sub-projects.", "A project is characterized by name, code, state, type, provisional and real dates, percent done.", "Distinct management teams can by composed of users, groups, suppliers and contacts.", "Several GANTT diagrams are available for each project (see tab GANTT).", "Project management relies on two types of items: project and project task." ] }, { "title": "Project tasks", "items": [ "This tab allows to add new tasks to the project. It displays also already defined tasks with, for each task, its name, type, status, planned start and end dates, real start and end dates, percent done and parent task name." ] }, { "title": "Project team", "items": [ "This tab allows to add new members to the project team, this member being a contact, a supplier or a group. It lists also members of project team with for each member its type." ] }, { "title": "Project", "items": [ "This tab displays project's sub-projects. A sub-project is defined the same way as a project, the only difference being that the field As child of is defined." ] }, { "title": "GANTT", "items": [ "A GANTT diagram is available for each project. A global GANTT diagram is also available, including projects defined as visible in this global diagram (field Show on global GANTT of the project form)." ] }, { "title": "Kanban", "items": [ "This tab provides an interface to use Kanban method.", "For more information about the Kanban feature, please refer to the full documentation ." ] }, { "title": "Costs", "items": [ "Costs can be attached to projects; the costs of the tickets attached to project's tasks will sum up to these costs." ] }, { "title": "ITIL objects", "items": [ "This tab allows to attach to the project GLPI ITIL objects: tickets, problems and changes. It is also possible to create these objects directly from this tab." ] }, { "title": "Project task", "items": [ "Task item is quite similar to a project.", "A project task can also be a project sub-task.", "A task is characterized by name, state, type, provisional and real dates, percent done.", "Distinct management teams can by composed of users, groups, suppliers and contacts.", "A project task is not an independent item, it can only be accessed through the Project tasks tab of the project owning the task.", "Tasks can be attached to tickets in order to plan interventions.", "Planned and actual duration are also defined for a task, reported at project level together with attached tickets duration." ] }, { "title": "Project tasks", "items": [ "This tab allows to display and add sub-tasks." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/projects.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/tools/projects.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/projects.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0066", "title": "Manage personal or public reminders", "category": "tools", "tags": [ "glpi", "documentation", "tools", "reminders" ], "relatedIssuePatterns": [ "tools", "reminders" ], "summary": "A reminder in GLPI is simple text with attached files; it allows to transmit information to other users of the platform.", "sections": [ { "title": "Overview", "items": [ "A reminder in GLPI is simple text with attached files; it allows to transmit information to other users of the platform.", "A reminder is characterized by:", "a lifetime;", "a status;", "the possibility to appear in planning;", "its targets.", "The created reminders will then appear in GLPI home page or in targeted users' planning.", "It is possible to add a start date and an end date for each reminder. If no start date is given, the reminder will be visible immediately and until its end date. If no end date is given, the reminder will be visible permanently starting from its start date.", "Adding a reminder to the planning makes it visible for targeted users of the reminder: the owner for a personal reminder, all users' plannings for a public note. A planned reminder is not deleted after its end date." ] }, { "title": "Target", "items": [ "A reminder is personal by default and therefore only visible for its writer.", "For a reminder to be visible by other users (public reminder), it is necessary to add targets to the reminder. Possible targets are entity, profile, group or users.", "A public reminder is visible by users associated with a profile if this profile has read permission for public reminders." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/reminders.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/tools/reminders.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/reminders.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0067", "title": "Generate reports", "category": "tools", "tags": [ "glpi", "documentation", "tools", "reports" ], "relatedIssuePatterns": [ "tools", "reports" ], "summary": "GLPI allows to generate reports based on managed items:", "sections": [ { "title": "Overview", "items": [ "GLPI allows to generate reports based on managed items:", "Default report", "This report summarizes present equipments sorted by type. Computers are also sorted by operating systems.", "By contract", "This report shows the equipments that are under a maintenance contract with a third-party and can be detailed by equipment type and purchase date.", "Multiple selection is available.", "To add a type, it is possible to click in empty area and choose new type. Same applies to add a date.", "Generated table lists, sorted by item type, name, if it is in trash bin, entity, location, purchase and warranty expire date, contract type and contract begin and end dates.", "By year", "Same as report by contract, but lists also the equipments without contract.", "Hardware financial and administrative information", "This report shows the summary of financial information for computers, printers, network equipments, displays, peripherals and phones.", "It is possible to obtain a report for a given period.", "The generated table lists, sorted by item type, name, entity, value, net accounting value, TCO, purchase date, starting date, warranty expire date. A summary displaying total value and net accountin value is available, both by item type and for all items.", "Other financial and administrative information", "Same as Hardware financial and administrative information, but for cartridges, licenses and consumables.", "Network report", "Three types of reports can be generated: by location, by hardware or by network plug.", "Loan", "This report shows a summary of current, future and past reservations for a given user.", "Status", "This report shows a summary of different status, sorted by equipment types.", "The range of possible reports can be increased by adding to GLPI the following plugin: https://plugins.glpi-project.org/#/plugin/reports" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/reports.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/tools/reports.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/reports.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0068", "title": "Manage reservations", "category": "tools", "tags": [ "glpi", "documentation", "tools", "reservations" ], "relatedIssuePatterns": [ "tools", "reservations" ], "summary": "GLPI includes an equipment reservation tool that allows to select assets in order to reserve them for a time slot. For repetitive reservations, it is possible to declare a reservation as recurrent.", "sections": [ { "title": "Overview", "items": [ "GLPI includes an equipment reservation tool that allows to select assets in order to reserve them for a time slot. For repetitive reservations, it is possible to declare a reservation as recurrent.", "By default, an equipment is not reservable!", "Making an equipment reservable is done from the Reservation tab of the equipment's form." ] }, { "title": "Add a reservation", "items": [ "To add a reservation, you can either :", "Go to the object to be reserved (depending on the profile authorizations)", "Go to Tools > Reservation (depending on the profile authorizations)", "Click on the desired date to display the reservation box", "If you have used the reservation tab of the GLPI object, the hardware will already be defined.", "If you've gone to the Tools > Reservation > View all items tab, you'll need to select the desired item.", "Select user if not already preselected", "Select the start date", "Select the duration (you can specify an end date if the reservation exceeds 1 day)", "Add a comment if it's necessary" ] }, { "title": "Add a repetition", "items": [ "If your booking is to be repeated or spread over several days/weeks/months, you can add a repeat to it" ] }, { "title": "Daily repetition", "items": [ "Select daily in repetition", "select the end date (the reservation will also be added to the last day selected)" ] }, { "title": "Weekly repetition", "items": [ "Select weekly in repetition", "select the end date (the reservation will also be added to the last day selected)", "Select the days on which the rehearsal will take place" ] }, { "title": "Monthly repetition", "items": [ "Select monthly in repetition", "select the end date (the reservation will also be added to the last day selected)", "In the dropdown list select :", "Each month, same date", "Each month, same day of weekly (for example, if your booking is on the Tuesday of the 2nd of the month,", "the repeat will take place on the same day of the following month.)" ] }, { "title": "View a reservation", "items": [ "A reserved equipment will be displayed in global reservation planning.", "It is also possible to consult the specific planning of a reservable equipment. A reservation can also be created from this planning.", "You can see all the reservation by clicking on View calendar for all items (Tools > Reservations)" ] }, { "title": "Find a free item", "items": [ "To simplify your equipment search, you can go to Tools > Reservation > Find a free item in a specific period", "If you don't have result, you can extend your search to all GLPI object types without all locations", "To proceed to booking click on booking calendar and follow the previous steps." ] }, { "title": "Delete or modify a reservation", "items": [ "You can modify a reservation by clicking on it. If you modify an occurrence, only the selected one is modified. If you wish to modify the whole series, you will either have to delete it and start again, or modify them one by one.", "To delete a reservation, click on it and click delete permanently. If you wish to delete all occurrences, you can click on delete all and delete permanently." ] }, { "title": "Disable reservation", "items": [ "From the GLPI object, you can deactivate the reservation or remove the reservation option.", "Make unavailable : deactivates the reservation feature, reservations are also deactivated.", "If the object is reservable again, the reservations that were present will be visible again.", "Prohibit reservations : deactivates and deletes all current reservations. The equipment can no longer be reserved." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/reservations.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/tools/reservations.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/reservations.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0069", "title": "Manage RSS feeds", "category": "tools", "tags": [ "glpi", "documentation", "tools", "rssfeed" ], "relatedIssuePatterns": [ "tools", "rssfeed" ], "summary": "GLPI allows to include RSS feeds in tool home page.", "sections": [ { "title": "Overview", "items": [ "GLPI allows to include RSS feeds in tool home page.", "A RSS feed is by default personal and therefore only visible by its creator.", "For a RSS feed to become public and visible by other users, targets must be added to it, a target being either an entity, a group, a profile or a user.", "A public RSS feed is visible by users associated with a profile if this profile has read permission for public RSS feeds." ] }, { "title": "Content", "items": [ "This tab allows to consult the number of displayed items; this content is the one displayed on home page." ] }, { "title": "Targets", "items": [ "This tab allows to display and modify the list of targets of the RSS feed." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/rssfeed.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/tools/rssfeed.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/tools/rssfeed.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0070", "title": "Cables", "category": "assets", "tags": [ "glpi", "documentation", "assets", "cables" ], "relatedIssuePatterns": [ "assets", "cables" ], "summary": "Any type of cable can be managed (ethernet, USB, HDMI, etc.). You can link a cable between 2 devices, and indicate the physical location where the cable is plugged into a device. You can also create tickets, problems, etc. from this cable for complete management", "sections": [ { "title": "Overview", "items": [ "Any type of cable can be managed (ethernet, USB, HDMI, etc.). You can link a cable between 2 devices, and indicate the physical location where the cable is plugged into a device. You can also create tickets, problems, etc. from this cable for complete management" ] }, { "title": "Add a cable", "items": [ "To add a cable on + Add at the top of the screen,", "Add a :", "Name", "Status", "Cable Type", "Technicien in charge", "Inventory number", "Comments", "Cable strand", "Color" ] }, { "title": "Cable Type", "items": [ "You can add the type of cable that links the hardware (USB, ethernet, HDMI, etc.).", "Select the type of cable required", "You can create a new one by clicking on +" ] }, { "title": "Enpoint", "items": [ "You can link 2 devices together to find out which cable connects them and on which socket To be linked to a socket, it must be specified on the hardware concerned", "To link two material by a cable, select the first object in endpoint A", "Type of asset", "The asset", "The socket model", "The socket", "If it is entered for the equipment in question, the position will be added.", "Do the same with endpoint B" ] }, { "title": "Management", "items": [ "If you have activated them, you can manage financial and administrative information" ] }, { "title": "Tickets", "items": [ "This tab lists all the tickets created for this object. You can not link a ticket here or create a new ticket. To link a object to a cable, go to Assistance > Ticket" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/cables.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/cables.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/cables.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0071", "title": "Cartridges", "category": "assets", "tags": [ "glpi", "documentation", "assets", "cartridges" ], "relatedIssuePatterns": [ "assets", "cartridges" ], "summary": "This functionality of Asset module allows to create cartridges models and corresponding cartridges.", "sections": [ { "title": "Overview", "items": [ "This functionality of Asset module allows to create cartridges models and corresponding cartridges.", "In a cartridge form, the following information is available:", "Name", "Location", "Cartridge type", "Reference", "Technician in charge", "Manufacturer", "Group in charge", "Comments", "Alert threshold", "Stock target", "Pictures" ] }, { "title": "Cartridges", "items": [ "It is also possible to add several cartridges at once." ] }, { "title": "Management", "items": [ "this information is visible in the 'Management' tab on the computer's form." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Links", "items": [ "Send the GLPI object file to another URL of your choice, or generate an RDP file, for example." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/cartridges.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/cartridges.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/cartridges.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0072", "title": "Computers", "category": "assets", "tags": [ "glpi", "documentation", "assets", "computers" ], "relatedIssuePatterns": [ "assets", "computers" ], "summary": "Each computer has its own information and related hardware (monitor, components, etc.). All this information is divided into tabs. You can find your computers in Assets > Computers:", "sections": [ { "title": "Overview", "items": [ "Each computer has its own information and related hardware (monitor, components, etc.). All this information is divided into tabs. You can find your computers in Assets > Computers:", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock" ] }, { "title": "Computer", "items": [ "Computer tab, includes basic information about the machine :", "Name", "Location", "Technician in charge", "Group in charge", "Alternate usernmame number", "Alternate usernmame", "User", "Group", "Comments", "Status", "Computer type", "Manufacturer", "Model", "Serial number", "Inventory number", "Network", "UUID", "Update source", "If your computer has been inventoried by the automatic inventory, you can find information about the GLPI Agent", "Agents", "Public contact address", "Agents Status", "Useragent", "Last contact", "Request inventory", "Inventory tag", "Last inventory update" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Operating systems", "items": [ "Name", "Version", "Architecture", "Service Pack", "Kernel", "Edition", "Product ID", "Serial number", "Company", "Owner", "Host ID", "Installation date" ] }, { "title": "Components", "items": [ "This tab lists the PC's components :", "BIOS", "Processor", "Memory", "Hard Drive", "Network card", "Drive", "Battery", "Graphics card", "Sound card", "Controller", "Each item has its own information (name, model, brand, memory capacity, number of cores/threads, etc.)." ] }, { "title": "Lines", "items": [ "You can add telephone lines created in Lines" ] }, { "title": "Volumes", "items": [ "Summarises all the volumes present (hard disk, DVD) as well as the partitions present on the workstation (virtual disks such as Google Cloud may appear if they are installed as a network drive).", "Name", "Automatic inventory (Yes /No)", "partition", "Mount point", "File system", "Global size", "Free size", "Free percentage", "Encryption (if the disk is encrypted, a padlock will be displayed)" ] }, { "title": "Software", "items": [ "Lists all the software brought up during the inventory and those added manually", "It is possible to install (in the logical sense) software on a PC manually.", "To add new software to the list of applications, you need to go to the Assets > Software tab, which will then be visible from the software tab of the various elements of the installed base." ] }, { "title": "Connections", "items": [ "The connections are all the other hardware connected to the machine :", "Device", "Monitor", "Phone", "Printers", "These items can be updated by the automatic inventory, but you can also connect them manually." ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to an equipment. The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/computers.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/computers.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/computers.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0073", "title": "Consumables", "category": "assets", "tags": [ "glpi", "documentation", "assets", "consumables" ], "relatedIssuePatterns": [ "assets", "consumables" ], "summary": "Consumables are items relating to resources or supplies intended to be used, loaned or entrusted as part of maintenance operations or the day-to-day running of an IT estate. These consumables generally include items such as USB sticks, HDMI cables or spare parts for hardware.", "sections": [ { "title": "Overview", "items": [ "Consumables are items relating to resources or supplies intended to be used, loaned or entrusted as part of maintenance operations or the day-to-day running of an IT estate. These consumables generally include items such as USB sticks, HDMI cables or spare parts for hardware.", "Apart from common actions , some actions are specific to consumables:", "Add new consumables to a model ;", "List allocated consumables:", "The Summary menu button allows you to see a summary of allocated consumables", "In a consumable form, the following information is available:", "Name", "Consumable type", "Technician in charge", "Group in charge", "User", "Comments", "Picture", "Location", "Reference", "Manufacturer", "Inventory number", "Group", "Alert threshold", "Stock target" ] }, { "title": "Consumables", "items": [ "In the Consumables tab, you can manage the quantities of consumables, allocate them to users/groups, put them back into stock, etc." ] }, { "title": "Management", "items": [ "this information is visible in the 'Management' tab on the computer's form." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Links", "items": [ "Send the GLPI object file to another URL of your choice, or generate an RDP file, for example." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/consumables.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/consumables.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/consumables.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0074", "title": "Enclosures", "category": "assets", "tags": [ "glpi", "documentation", "assets", "enclosures" ], "relatedIssuePatterns": [ "assets", "enclosures" ], "summary": "An enclosure is a type of equipment used to manage modular infrastructures, such as blade servers, storage bays or certain network equipment.", "sections": [ { "title": "Overview", "items": [ "An enclosure is a type of equipment used to manage modular infrastructures, such as blade servers, storage bays or certain network equipment.", "It enables several physical elements to be grouped together in the same box, while retaining individual management of the components.", "When you add an enclosure (by + Add at the top of the screen), you can add certain information:", "Name", "Location", "Technician in charge", "Manufacturer", "Serial number", "User", "Power Supplies (number of power supplies)", "Status", "Technician in charge", "Model", "Inventory number", "Comments" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Components", "items": [ "Enclosure has specific :doc:`Setup > Components <../../configuration/components>` compared with other equipment since this is rather passive equipment that contains no software, firmware, etc.", "You can add a :", "Generic device", "PCI device", "Power supply." ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to an equipment. The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of file to current item (PDF, txt, png, etc.)", "You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Tickets", "items": [ "View all tickets linked to the enclosure" ] }, { "title": "Problems", "items": [ "This tab refers to all hardware-related problems . Problems can also be linked to tickets, projects, etc. This allows you to have a complete scenario when necessary." ] }, { "title": "Changes", "items": [ "You can create a new change from this page, which will be linked to current item." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/enclosures.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/enclosures.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/enclosures.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0075", "title": "Global search", "category": "assets", "tags": [ "glpi", "documentation", "assets", "global" ], "relatedIssuePatterns": [ "assets", "global" ], "summary": "Menu `Asset > Global` allows to perform a global search on default view columns for allowed elements. This search is limited to following assets:", "sections": [ { "title": "Overview", "items": [ "Menu `Asset > Global` allows to perform a global search on default view columns for allowed elements. This search is limited to following assets:", "Computers", "Contacts", "Contracts", "Documents", "Monitors", "Network Equipments", "Peripherals", "Phones", "Printers", "Softwares", "Software Licenses", "Tickets", "Problems", "Changes", "Users", "Groups", "Projects", "Suppliers", "Budgets", "Certificates", "Lines", "Datacenters", "Server Rooms", "Enclosure", "PDU", "Rack", "Cluster", "Passive Devices", "Domains", "Appliances", "This search allows for instance to perform a query by status, IP or MAC address." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/global.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/global.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/global.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0076", "title": "Monitors", "category": "assets", "tags": [ "glpi", "documentation", "assets", "monitors" ], "relatedIssuePatterns": [ "assets", "monitors" ], "summary": "Each monitor has its own information (connections, contrats, network ports, etc.). All this information is divided into tabs. You can find your computers in Assets > Monitors:", "sections": [ { "title": "Overview", "items": [ "Each monitor has its own information (connections, contrats, network ports, etc.). All this information is divided into tabs. You can find your computers in Assets > Monitors:", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock", "In a display form, the following information is available:", "Name", "Location", "Technician in charge", "Group in charge", "Alternate usernmame number", "Alternate usernmame", "User", "Group", "Size", "UUID", "Update source", "Status", "Monitor type", "Manufacturer", "Model", "Serial number", "Inventory number", "Network", "Management type", "Comments", "Ports", "Management type:", "It is possible to manage displays either unitary or globally.", "Unitary management corresponds to one display per computer while global management make the printer a virtual global element that will be connected to several computers.", "Global management allows to limit the number of elements to manage when these elements are not a strategic data in the assets management.", "It is possible to use templates with displays ." ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Operating systems", "items": [ "Name", "Version", "Architecture", "Service Pack", "Kernel", "Edition", "Product ID", "Serial number", "Company", "Owner", "Host ID", "Installation date" ] }, { "title": "Software", "items": [ "Lists all the software brought up during the inventory and those added manually", "It is possible to install (in the logical sense) software on a PC manually.", "To add new software to the list of applications, you need to go to the Assets > Software tab, which will then be visible from the software tab of the various elements of the installed base." ] }, { "title": "Connections", "items": [ "The connections are all the other hardware connected to the machine :", "Computer", "Other asset you have created", "These items can be updated by the automatic inventory, but you can also connect them manually." ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to an equipment. The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Knowledge Base", "items": [ "Lists all the articles in the knowledge base relating to the material." ] }, { "title": "Tickets", "items": [ "View all tickets linked to the computer" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/monitors.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/monitors.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/monitors.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0077", "title": "Network equipments", "category": "assets", "tags": [ "glpi", "documentation", "assets", "network-equipments" ], "relatedIssuePatterns": [ "assets", "network-equipments" ], "summary": "Network equipment represent the hardware that manages, transmits and route network between several other equipments (computers, printers...).", "sections": [ { "title": "Overview", "items": [ "Network equipment represent the hardware that manages, transmits and route network between several other equipments (computers, printers...).", "A network equipment can be a switch, an Ethernet hub, a router, a firewall or a WiFi access point.", "It is possible to use templates with network equipments .", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock" ] }, { "title": "Network device", "items": [ "Network device tab, includes basic information about the material :", "Name", "Data center position", "Location", "Technician in charge", "Group in charge", "Alternate usernmame number", "Alternate usernmame", "User", "Group", "Comments", "Status", "Network equipment type", "Manufacturer", "Model", "Serial number", "Inventory number", "Network", "UUID", "Update source", "If your computer has been inventoried by the automatic inventory, you can find information about the GLPI Agent", "Agents", "Public contact address", "Agents Status", "Useragent", "Last contact", "Request inventory", "Inventory tag", "Last inventory update" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Operating systems", "items": [ "Name", "Version", "Architecture", "Service Pack", "Kernel", "Edition", "Product ID", "Serial number", "Company", "Owner", "Host ID", "Installation date" ] }, { "title": "Software", "items": [ "Lists all the software brought up during the inventory and those added manually", "It is possible to install (in the logical sense) software on a device manually.", "To add new software to the list of applications, you need to go to the Assets > Software tab, which will then be visible from the software tab of the various elements of the installed base." ] }, { "title": "Components", "items": [ "This tab lists the PC's components :", "BIOS", "Processor", "Memory", "Hard Drive", "Network card", "Drive", "Battery", "Graphics card", "Soundcard", "Controller", "Each item has its own information (name, model, brand, memory capacity, number of cores/threads, etc.)." ] }, { "title": "Lines", "items": [ "You can add telephone lines created in Lines" ] }, { "title": "Volumes", "items": [ "Summarises all the volumes present (hard disk, DVD) as well as the partitions present on the workstation (virtual disks such as Google Cloud may appear if they are installed as a network drive).", "Name", "Automatic inventory (Yes /No)", "partition", "Mount point", "File system", "Global size", "Free size", "Free percentage", "Encryption (if the disk is encrypted, a padlock will be displayed)" ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to an equipment. The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] }, { "title": "Network Name", "items": [ "They usually appear as a dropdown list and are useful for defining specific network categories or contexts.", "The visible fields are :", "Network name", "IP addresses", "IP networks" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/network-equipments.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/network-equipments.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/network-equipments.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0078", "title": "Passive devices", "category": "assets", "tags": [ "glpi", "documentation", "assets", "passives-devices" ], "relatedIssuePatterns": [ "assets", "passives-devices" ], "summary": "Passive devices list equipment that do not actively process data but still play an essential role in the IT infrastructure. They are often used for connectivity or signal transmission (like a patch panel, a non-manageable switch, etc.)", "sections": [ { "title": "Overview", "items": [ "Passive devices list equipment that do not actively process data but still play an essential role in the IT infrastructure. They are often used for connectivity or signal transmission (like a patch panel, a non-manageable switch, etc.)", "In a passive device form, the following information is available:", "Name", "Location", "Technician in charge", "Model", "Inventory number", "Comments", "Status", "Passive device type", "Manufacturer", "Serial number", "User" ] }, { "title": "Sockets", "items": [ "It enables hardware to be linked by cables. Socket is also linked to the cables object" ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of files to the current item (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Tickets", "items": [ "View all tickets linked to the current item." ] }, { "title": "Problems", "items": [ "This tab refers to all hardware-related problems . Problems can also be linked to tickets, projects, etc. This allows you to have a complete scenario when necessary." ] }, { "title": "Changes", "items": [ "You can create a new change from this page, which will be linked to the item you have selected." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/passives_devices.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/passives_devices.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/passives_devices.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0079", "title": "PDUs", "category": "assets", "tags": [ "glpi", "documentation", "assets", "pdus" ], "relatedIssuePatterns": [ "assets", "pdus" ], "summary": "In a PDU form, the following information is available:", "sections": [ { "title": "Overview", "items": [ "In a PDU form, the following information is available:", "Name", "Data center position", "Location", "Technician in charge", "Model", "Inventory number", "Comments", "Status", "Device type", "Manufacturer", "Serial number", "User" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to current item.", "The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of files to the item (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Tickets", "items": [ "View all tickets linked to the item." ] }, { "title": "Problems", "items": [ "This tab refers to all hardware-related problems . Problems can also be linked to tickets, projects, etc. This allows you to have a complete scenario when necessary." ] }, { "title": "Changes", "items": [ "You can create a new change from this page, which will be linked to the item you have selected." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/pdus.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/pdus.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/pdus.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0080", "title": "Peripherals", "category": "assets", "tags": [ "glpi", "documentation", "assets", "peripherals" ], "relatedIssuePatterns": [ "assets", "peripherals" ], "summary": "Peripherals object refers to ancillary equipment or accessories connected to a main system (computer, server, etc.). This includes hardware elements required to operate or extend the capabilities of a workstation or network.", "sections": [ { "title": "Overview", "items": [ "Peripherals object refers to ancillary equipment or accessories connected to a main system (computer, server, etc.). This includes hardware elements required to operate or extend the capabilities of a workstation or network.", "In a peripheral form, the following information is available:", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock", "Name", "Location", "Technician in charge", "Group in charge", "Alternate usernmame number", "Alternate usernmame", "User", "Group", "Comments", "Status", "Device type", "Manufacturer", "Model", "Serial number", "Inventory number", "Management type", "Network", "UUID", "Update source" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Operating systems", "items": [ "Name", "Version", "Architecture", "Service Pack", "Kernel", "Edition", "Product ID", "Serial number", "Company", "Owner", "Host ID", "Installation date" ] }, { "title": "Software", "items": [ "Lists all the software brought up during the inventory and those added manually", "It is possible to install (in the logical sense) software on a PC manually.", "To add new software to the list of applications, you need to go to the Assets > Software tab, which will then be visible from the software tab of the various elements of the installed base." ] }, { "title": "Components", "items": [ "This tab lists the PC's components :", "BIOS", "Processor", "Memory", "Hard Drive", "Network card", "Drive", "Battery", "Graphics card", "Soundcard", "Controller", "Each item has its own information (name, model, brand, memory capacity, number of cores/threads, etc.)." ] }, { "title": "Lines", "items": [ "You can add telephone lines created in Lines" ] }, { "title": "Connections", "items": [ "The connections are all the other hardware connected to the machine :", "Device", "Monitor", "Phone", "Printers", "These items can be updated by the automatic inventory, but you can also connect them manually." ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to an equipment. The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] }, { "title": "Sockets", "items": [ "This information cannot be returned by the automatic inventory, so you have to add it manually.", "It enables hardware to be linked by cables. Socket is also linked to the cables object" ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/peripherals.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/peripherals.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/peripherals.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0081", "title": "Phones", "category": "assets", "tags": [ "glpi", "documentation", "assets", "phones" ], "relatedIssuePatterns": [ "assets", "phones" ], "summary": "Phones can be registered manually or uploaded using the Android agent (no agent is currently compatible with iPadOS/iOS devices).", "sections": [ { "title": "Overview", "items": [ "Phones can be registered manually or uploaded using the Android agent (no agent is currently compatible with iPadOS/iOS devices).", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock", "In a phone form, the following information is available:", "Name", "Location", "Technician in charge", "Group in charge", "Alternate usernmame number", "Alternate usernmame", "User", "Group", "Comments", "Status", "Phone type", "Manufacturer", "Model", "Serial number", "Inventory number", "Management type", "UUID", "Brand", "Number of lines", "Update source", "Ports" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Operating systems", "items": [ "Name", "Version", "Architecture", "Service Pack", "Kernel", "Edition", "Product ID", "Serial number", "Company", "Owner", "Host ID", "Installation date" ] }, { "title": "Components", "items": [ "This tab lists the phone's components :", "BIOS", "Processor", "Memory", "Hard Drive", "Network card", "Drive", "Battery", "Graphics card", "Soundcard", "Controller", "Each item has its own information (name, model, brand, memory capacity, number of cores/threads, etc.)." ] }, { "title": "Lines", "items": [ "You can add telephone lines created in Lines" ] }, { "title": "Volumes", "items": [ "Summarises all of the volumes present (hard disk, DVD) as well as the partitions present on the workstation (virtual disks such as Google Cloud may appear if they are installed as a network drive).", "Name", "Automatic inventory (Yes /No)", "partition", "Mount point", "File system", "Global size", "Free size", "Free percentage", "Encryption (if the disk is encrypted, a padlock will be displayed)" ] }, { "title": "Connections", "items": [ "It is possible to create a connections with a telephone using the following element:", "Computer" ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to an equipment. The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] }, { "title": "Sockets", "items": [ "This information cannot be returned by the automatic inventory, so you have to add it manually.", "It enables hardware to be linked by cables. Socket is also linked to the cables object" ] }, { "title": "Remote management", "items": [ "It is possible to add software manually if required, but the information can be fed back via the automatic inventory." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/phones.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/phones.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/phones.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0082", "title": "Printers", "category": "assets", "tags": [ "glpi", "documentation", "assets", "printers" ], "relatedIssuePatterns": [ "assets", "printers" ], "summary": "Printers can be brought up via SNMP discovery or manually. Certain information such as ink level or page counter can be fed in.", "sections": [ { "title": "Overview", "items": [ "Printers can be brought up via SNMP discovery or manually. Certain information such as ink level or page counter can be fed in.", "In a printer form, the following information is available:", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock", "Name", "Location", "Technician in charge", "Group in charge", "Alternate usernmame number", "Alternate usernmame", "Sysdescr", "User", "Group", "Comments", "Status", "Printer type", "Manufacturer", "Model", "Serial number", "Inventory number", "SNMP Credentials", "Management type", "Network", "UUID", "Update source", "Memory" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Operating systems", "items": [ "Name", "Version", "Architecture", "Service Pack", "Kernel", "Edition", "Product ID", "Serial number", "Company", "Owner", "Host ID", "Installation date" ] }, { "title": "Software", "items": [ "Lists all the software brought up during the inventory and those added manually", "It is possible to install (in the logical sense) software on a PC manually.", "To add new software to the list of applications, you need to go to the Assets > Software tab, which will then be visible from the software tab of the various elements of the installed base." ] }, { "title": "Cartridges", "items": [ "If they are reported by the inventory, the ink level will also be indicated." ] }, { "title": "Page counters", "items": [ "If the printer allows it (this depends on the information that the manufacturer authorises), the number of prints can be reduced. If the printer allows it (this depends on the information the manufacturer allows), the number of prints can be reduced. A filter is available for viewing the last 7 or 30 days, the last year, etc. or for viewing daily, weekly, etc. printouts. You can also compare the number of prints against another printer." ] }, { "title": "Components", "items": [ "This tab lists the PC's components :", "BIOS", "Processor", "Memory", "Hard Drive", "Network card", "Drive", "Battery", "Graphics card", "Soundcard", "Controller", "Each item has its own information (name, model, brand, memory capacity, number of cores/threads, etc.)." ] }, { "title": "Lines", "items": [ "You can add telephone lines created in Lines" ] }, { "title": "Volumes", "items": [ "Summarises all the volumes present (hard disk, DVD) as well as the partitions present on the workstation (virtual disks such as Google Cloud may appear if they are installed as a network drive).", "Name", "Automatic inventory (Yes /No)", "partition", "Mount point", "File system", "Global size", "Free size", "Free percentage", "Encryption (if the disk is encrypted, a padlock will be displayed)" ] }, { "title": "Connections", "items": [ "The connections are all the other hardware connected to the machine :", "Device", "Monitor", "Phone", "Printers", "These items can be updated by the automatic inventory, but you can also connect them manually." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/printers.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/printers.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/printers.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0083", "title": "Racks", "category": "assets", "tags": [ "glpi", "documentation", "assets", "racks" ], "relatedIssuePatterns": [ "assets", "racks" ], "summary": "A rack is a piece of equipment such as a patch bay or computer cabinet used to organize, host and physically connect different network equipments and servers in a datacenter or technical room.", "sections": [ { "title": "Overview", "items": [ "A rack is a piece of equipment such as a patch bay or computer cabinet used to organize, host and physically connect different network equipments and servers in a datacenter or technical room.", "A rack is a dedicated object in GLPI that virtually represents the physical structure of a rack or cabinet. It is designed to :", "Organize equipment: A rack is used to visualize and manage the physical equipment (servers, switches, routers, UPS, etc.)", "installed in it.", "Facilitate physical management: It enables you to track where equipment is installed in a physical space (technical room, datacenter, etc.).", "Optimize space: Racks help ensure that space is used efficiently, and that there's still room for new equipment.", "When you add a rack (by + Add at the top of the screen), you can add certain information:", "Name", "Data center position", "Location", "Technician in charge", "Group in charge", "Serial number", "User", "Comments", "Position in room", "Number of units", "Height", "Max. Power (in watts)", "Max. weight", "Status", "Rack type", "Manufacturer", "Model", "Inventory number", "Group", "Server room", "Door orientation in room (North, East, South, West)", "Width", "Depth", "Measured power (in watts)", "Background color" ] }, { "title": "Items", "items": [ "The Item tab shows the position of each element in the rack. You can modify, add or remove an item from your park to your rack." ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Tickets", "items": [ "View all tickets linked to the computer" ] }, { "title": "Problems", "items": [ "This tab refers to all hardware-related problems . Problems can also be linked to tickets, projects, etc. This allows you to have a complete scenario when necessary." ] }, { "title": "Changes", "items": [ "You can create a new change from this page, which will be linked to the material you have selected." ] }, { "title": "Reservations", "items": [ "The reservation tab lets you reserve equipment, view the reservation schedule, or cancel the possibility of reserving this equipment. By default, equipment cannot be reserved; you must first authorize this action manually." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/racks.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/racks.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/racks.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0084", "title": "SIM", "category": "assets", "tags": [ "glpi", "documentation", "assets", "sim" ], "relatedIssuePatterns": [ "assets", "sim" ], "summary": "A SIM (Subscriber Identity Module) represents a SIM card used in mobile equipment such as telephones, tablets, 4G/5G modems, etc. You can manage these SIM cards as specific objects to track their use and allocation.", "sections": [ { "title": "Overview", "items": [ "A SIM (Subscriber Identity Module) represents a SIM card used in mobile equipment such as telephones, tablets, 4G/5G modems, etc. You can manage these SIM cards as specific objects to track their use and allocation.", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock", "In a display form, the following information is available:", "Code PIN", "Code PIN2", "Code PUK", "Code PUK2", "Line", "Mobile Subscriber Identification Number (MSIN is last 8 or 10 digits of IMSI)", "Serial number", "Inventory number", "Location", "Status", "User", "Group", "Comments" ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of files to this item (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Locks", "items": [ "You can lock/unlock the fields you wish in a GLPI object." ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management, in order to manage contract types such as loan, maintenance, support...", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/sim.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/sim.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/sim.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0085", "title": "Software", "category": "assets", "tags": [ "glpi", "documentation", "assets", "softwares" ], "relatedIssuePatterns": [ "assets", "softwares" ], "summary": "GLPI allows management of software and their versions as well as licenses, associated or not to software versions.", "sections": [ { "title": "Overview", "items": [ "GLPI allows management of software and their versions as well as licenses, associated or not to software versions.", "A software is by default associated with an entity.", "Financial management is done at the level of licenses; the financial management at software level is only a model for the licenses associated with this software.", "Software can be imported automatically using a third-party inventory tool; in this case a dictionary can be used to filter or clean the import data (see Configure data dictionaries . Dictionaries are managed from menu entry Administration > Dictionaries).", "It is recommended to first create the software without a version number in the name, then to create the versions and last to create the licenses.", "In multi-entity mode, the list of software can rapidly become long because of double entries (one software per entity). A better approach can consist in grouping identical software in the same entity (see tab Grouping below), then to make recursive the elements that can be made recursive.", "It is possible to use templates with software .", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock", "Name", "Location", "Technician in charge", "Group in charge", "User", "Group", "Comments", "Pictures", "Some fields are specific in the software form:", "Upgrade From is an information, with no processing associated and which tells whether the software is an update of another software", "Software category allows to group software in the list of software of an asset", "Associable to a ticket defines whether the software can be seen in the drop-down list \"Hardware\" of a ticket" ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Versions", "items": [ "A version of a software is the element that can be installed on a asset; see also Installations tab .", "The main view lists the number of installations of the version.", "Name: the version number", "Status: in ITIL recommendations, it allows to follow the DSL (library storing authorized versions)", "Operating system: the operating system on which this software version runs", "Summary: overview of installations and entities in which the software is installed", "Installations: the number of installations of the version", "Historical: historical of the events", "All: all previous elements" ] }, { "title": "Licenses", "items": [ "to know who is using a license, how many are available and how many are being used. GLPI makes it possible to associate costs with licenses, which facilitates budget management. Licenses can be linked to equipment (computers, servers, etc.) or to specific users, so you know who is using what. It is also possible to set up expiry alerts.", "Here are the fields available from this tab:", "Name", "Serial number", "Number", "Affected Items", "Type", "Purchase version", "Version in use", "Expiration", "Status" ] }, { "title": "Installations", "items": [ "The installation of a software on a computer is visualized through a version and can be consulted on a software form (list of computers having at least one version installed), on a version form (computers having this version installed) and finally on a computer form (list of versions of installed software, sorted by category).", "Column license is filled only when the license is affected to the concerned computer", "The initial display of different categories depend upon user preferences. See manage preferences", "Two options are available on the list of installations of software on a computer. Above the list, Install allows to install manually a version of a software on the computer, by selecting first the software and its version; if a license is associated with this software, the use version of the license is automatically selected.", "To Uninstall a version of a software, mass actions must be used: first select the versions to be uninstalled, then select Suppress definitively. If a license is affected to the computer, it remains affected but its use version is erased.", "Following the list of installed versions, the list of affected but non installed licenses is displayed. It is possible to add a new license to the computer. Mass actions allow, via the action Install, to install a use version of selected licenses." ] }, { "title": "Management", "items": [ "this information is visible in the 'Management' tab on the software's form." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Knowledge Base", "items": [ "Lists all the articles in the knowledge base relating to the item." ] }, { "title": "Tickets", "items": [ "View all tickets linked to the software" ] }, { "title": "Problems", "items": [ "This tab refers to all hardware-related problems . Problems can also be linked to tickets, projects, etc. This allows you to have a complete scenario when necessary." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/softwares.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/softwares.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/softwares.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0086", "title": "Antivirus", "category": "assets", "tags": [ "glpi", "documentation", "assets", "antivirus" ], "relatedIssuePatterns": [ "assets", "antivirus" ], "summary": "This tab, named Antivirus and visible in a Computer entry, allows to manage the antivirus running on a computer.", "sections": [ { "title": "Overview", "items": [ "This tab, named Antivirus and visible in a Computer entry, allows to manage the antivirus running on a computer.", "An antivirus is characterized by:", "Name", "Automatic inventory", "Manufacturer", "Antivirus version", "Signature database version", "Active/non active", "Update to date", "Expiration date", "Every deletion or addition of an antivirus is recorded in the history of the computer.", "If using native inventory or third-party inventory tool, the antivirus information can be automatically imported and updated." ] }, { "title": "Add an antivirus", "items": [ "Click on Add an antivirus", "Enter the information of the antivirus", "If the manufacturer does not exist, you can add one", "expiration date is for administrative purposes only, to find out the antivirus expiry date." ] }, { "title": "Delete an antivirus", "items": [ "To delete an antivirus, you just need to click on Delete permanently", "If the antivirus is still present on the workstation, it will be brought up during the next automatic inventory. You will also have to delete it on the workstation in question." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/antivirus.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/antivirus.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/antivirus.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0087", "title": "Components", "category": "assets", "tags": [ "glpi", "documentation", "assets", "components" ], "relatedIssuePatterns": [ "assets", "components" ], "summary": "This tab, named Components and visible in a Computer entry, allows to manage the hardware components of a computer.", "sections": [ { "title": "Overview", "items": [ "This tab, named Components and visible in a Computer entry, allows to manage the hardware components of a computer.", "Adding or managing components is located in menu :doc:`Setup > Components </modules/configuration/components>`.", "If several components of the same type are used, they will be grouped in the view.", "It is possible to add a component by first selecting its family in the drop-down list at the top of the table and then its name and the number of components to add.", "Starting from a computer view, it is possible to modify a component by clicking on the link under its name.", "To act on several components (for example modify an element of the component, activate accounting information or modify them, delete a component...), first select the components and then use the Actions button present at the top or the bottom of the list.", "If several types of different components, not having the same characteristics, are selected for modification, in the actions it will be asked on which component modification must be applied.", "Selection button in left column allows to select all the components at once.", "Selection at right of type column (grayed line) allows to select all components of the same type (processor, memory, network interface...).", "It is possible to modify the characteristics of a component only for one computer", "From tab Elements of the component, click on the link Update.", "Several tabs are then displayed:", "Tab \"Element - Link name of component\" : list the characteristics of this component", "Tab \"Management\" : manage administrative and accounting information", "Tab \"Documents\" : attached documents", "Tab \"History\" : history of modifications", "Tab \"Contract\" : contracts management", "Tab \"Debug\" : only if you are connected in Debug mode", "Tab \"All\" : all the information are displayed on a single page", "Every deletion or addition of a component is recorded in the history of the computer.", "If using native inventory or third-party inventory tool, the components information can be automatically imported and updated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/components.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/components.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/components.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0088", "title": "Connections", "category": "assets", "tags": [ "glpi", "documentation", "assets", "connexions" ], "relatedIssuePatterns": [ "assets", "connexions" ], "summary": "This tab allows to manage the direct connections between a computer and its connected elements.", "sections": [ { "title": "Overview", "items": [ "This tab allows to manage the direct connections between a computer and its connected elements.", "Direct connections represent the relation between different hardwares linked either physically or virtually." ] }, { "title": "From a computer", "items": [ "The connection can be made toward one or several elements of type display, printer, peripheral or phone. For each type of connected object, its name, serial number and inventory number are displayed." ] }, { "title": "From an element other than a computer", "items": [ "To add a connection, select the computer in the drop-down list presented at top of the table.", "If this case, the connection can only be made to a single computer. The table will list the name of this computer as well as its serial and inventory numbers.", "The deletion of a connection can be made from the entry of each connected hardware (tab Connections) via mass actions.", "Every deletion or addition of a connection is recorded in the history of the computer.", "If using native inventory or third-party inventory tool, the connections information can be automatically imported and updated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/connexions.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/connexions.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/connexions.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0089", "title": "Items", "category": "assets", "tags": [ "glpi", "documentation", "assets", "enclosures-items" ], "relatedIssuePatterns": [ "assets", "enclosures-items" ], "summary": "This tab displays the list of items linked to the chassis. This allows for better organisation and simplified management thanks to a centralised view.", "sections": [ { "title": "Overview", "items": [ "This tab displays the list of items linked to the chassis. This allows for better organisation and simplified management thanks to a centralised view." ] }, { "title": "Add a item", "items": [ "To add an item (this item must already exist in your glpi), click on Add new item to this enclosure", "Select the item type (computer, monitor, network device, peripheral, PDU, passive device)", "Select the required item", "Select the enclosure in which the item is to be positioned", "Choose a position", "Click on + Add" ] }, { "title": "Delete an item", "items": [ "To delete an item from enclosure, use the massive action :" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/enclosures_items.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/enclosures_items.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/enclosures_items.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0090", "title": "Locks", "category": "assets", "tags": [ "glpi", "documentation", "assets", "locks" ], "relatedIssuePatterns": [ "assets", "locks" ], "summary": "Locks prevent certain information from being modified during automatic inventory feedback. These locks are activated when a manual modification has been made.", "sections": [ { "title": "Overview", "items": [ "Locks prevent certain information from being modified during automatic inventory feedback. These locks are activated when a manual modification has been made." ] }, { "title": "Lock a field", "items": [ "To lock a field, you need to modify the data of this field manually.", "When a field is modified manually, a padlock appears next to the title :" ] }, { "title": "Unlock a field", "items": [ "To unlock a field, go to the GLPI object on which the lock is located", "In the lock tab, click on the checkbox of the item to unlock", "Click on Actions", "Then Delete permanently", "And Post", "The padlock is no longer present on the field and can now be modified by the automatic inventory.", "All changes will be stored in the historical tab." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/locks.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/locks.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/locks.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0091", "title": "Network ports", "category": "assets", "tags": [ "glpi", "documentation", "assets", "network-ports" ], "relatedIssuePatterns": [ "assets", "network-ports" ], "summary": "This tab, named Network ports and visible in a Computer entry, allows to manage the network ports attached to a computer.", "sections": [ { "title": "Overview", "items": [ "This tab, named Network ports and visible in a Computer entry, allows to manage the network ports attached to a computer.", "A network port represents the output of a network interface on a given hardware. A port is characterized by a number and a name.", "It is possible on a network port to add one or more VLAN, these VLANs being defined by a name, an optional comment and a VLAN number.", "One or more network name can be associated to each network port. This can be done in tab Network name.", "When a network port has only one network name, this name is displayed in the network port form itself and it is possible to modify the name directly. It is also possible to modify the network name via its own form, accessible by clicking on the link under the name.", "When a network port has several network names, the only way to modify the network names is via the network name form.", "Network ports can be of different types:", "physical port: ethernet, WiFi...", "Virtual network port: local loop-back, alias, aggregates...", "point to point: switched network...", "The Network port tab groups in a table the ports that are available on the equipment. The table header contains the total number of ports and a link that allows to choose display options. This allows to selectively display or mask information such as network data (IP...), port characteristics depending on its type, MAC address, VLANs...", "GLPI allows to present complex network connection with for example WiFi or Ethernet port aliases associated to VLANs grouped in aggregates..." ] }, { "title": "Management of Ethernet network ports", "items": [ "The Ethernet protocol is classically used on internal networks.", "An Ethernet port is characterized by its type (twisted pair, mono-mode/multi-mode optical fiber...), a transfer rate ((10Mb, 100Mb, 1Gb, 10Gb...) and a MAC address. It is possible to associate to the port a network card and a network plug.", "Ethernet connections are realized by linking two Ethernet ports, which requires that there is a free port on each equipment to be connected. In general, a connection links a port attached to a computer, a peripheral or a printer and a port attached to a network equipment (hub, switch)." ] }, { "title": "Management of WiFi network ports", "items": [ "The WiFi protocol is widely used on wireless networks.", "A WiFi port is characterized by the mode of the network card (ad-hoc, access point, repeater...), the WiFi protocol version (ab, g...) and its MAX address.", "It is possible to associate a network card to the port, similarly to Ethernet ports.", "A WiFi network can be associated to a given port. Apart from its name, a WiFi network has an ESSID and is characterized by its type:", "Infrastructure: WiFi network with on or several access points and connected clients Ad-hoc: WiFi network between similar systems without access points" ] }, { "title": "Management of local loop-back ports", "items": [ "The local loop-back is a virtual port used by most equipments for internal communication. It is this port that is used when connecting to `localhost or 127.0.0.1`.", "Local loop-back has no specific attribute." ] }, { "title": "Management of network port aliases", "items": [ "A network port alias is a virtual port that can refine a physical port.", "On Linux, to each VLAN, when transmitted \"tagged\" _, is associated a port alias, for example eth2.50 to represent VLAN 50 on port eth2.", "A port alias contains its base port and a MAC address.", "Note that when the origin port is changed, the MAC address of the new port is affected to the port alias." ] }, { "title": "Management of network port aggregates", "items": [ "A network port aggregate is a virtual port that allows to group several physical ports.", "On Linux, aggregates are represented by bridges bridges linking together different ports. In the same way, an Ethernet firewall uses a bridge that links interfaces to be filtered.", "A port aggregate contains the origin ports and a MAC address.", "Every deletion or addition of a network port is recorded in the history of the computer.", "If using native inventory or third-party inventory tool, the network ports information can be automatically imported and updated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/network-ports.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/network-ports.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/network-ports.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0092", "title": "Network Name", "category": "assets", "tags": [ "glpi", "documentation", "assets", "network-name" ], "relatedIssuePatterns": [ "assets", "network-name" ], "summary": "A network name is the unique identification of a machine from the Internet point of view.", "sections": [ { "title": "Overview", "items": [ "A network name is the unique identification of a machine from the Internet point of view.", "Generally, a device is identified by one or more particular names on the network. The DNS server will resolve this name to an IP address. In case both IPv4 and IPv6 are used, this name will return two IP addresses: one in IPv4 and the other in IPv6. This is why a network name can have several IP addresses.", "A network name is composed of a name that corresponds to the FQDN label and one or more IP addresses.", "The IP network field appears in order to retrieve information about the different IP networks available. This information is not kept in the network name because it can have several IP addresses and each can belong to several IP networks.", "When entering a network name, the validity of the name as well as that of each IP address is checked. If one of these elements is not valid then it is rejected.", "To add an IP address to a network name, click on the + Add in front of the IP address entry fields. To remove an IP address, simply delete the contents of the IP field you wish to remove." ] }, { "title": "Network alias", "items": [ "Displays a list of aliases for this network and allows adding new ones.", "Traditionally, the network name is the one used by DNS for reverse resolution of an IP address, while the aliases correspond to the CNAME of the FQDN name.", "Similarly, the alias name must have a valid FQDN label" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/network_name.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/network_name.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/network_name.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0093", "title": "Operating systems", "category": "assets", "tags": [ "glpi", "documentation", "assets", "os" ], "relatedIssuePatterns": [ "assets", "os" ], "summary": "The information on operating systems for a computer are visible in tabs Operating system for a Computer entry.", "sections": [ { "title": "Overview", "items": [ "The information on operating systems for a computer are visible in tabs Operating system for a Computer entry.", "An operating system is associated with the following elements:", "Name", "Version", "Architecture", "Service Pack", "Kernel", "Edition", "Product ID", "Serial number", "The creation and management of the titles for operating systems is located in the menu `Setup > Drop-downs > Operating systems`.", "A deletion or addition of an operating system is recorded in the history of the computer.", "If using native inventory or third-party inventory tool, the operation system information can be automatically imported and updated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/os.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/os.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/os.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0094", "title": "Plugs", "category": "assets", "tags": [ "glpi", "documentation", "assets", "plugs" ], "relatedIssuePatterns": [ "assets", "plugs" ], "summary": "This tab shows the number of plugs available on a PDU. This item can be linked to a rack or an enclosure", "sections": [ { "title": "Overview", "items": [ "This tab shows the number of plugs available on a PDU. This item can be linked to a rack or an enclosure" ] }, { "title": "Add a plug", "items": [ "To add a plug on PDU, choose the type of plug you require from the drop-down list", "Select a number of plugs available on the PDUs", "Click on Add" ] }, { "title": "Delete a plug", "items": [ "To delete a plug, use the massive action :", "Select the plug", "Click on Actions", "Select Delete permanently the relation with selected elements", "Click on Post" ] }, { "title": "Create a plug", "items": [ "If the plug model you want is not available, you can create a new one.", "Click on +", "Fill in the fields", "Click on +Add" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/plugs.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/plugs.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/plugs.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0095", "title": "Items", "category": "assets", "tags": [ "glpi", "documentation", "assets", "rack-items" ], "relatedIssuePatterns": [ "assets", "rack-items" ], "summary": "Racks enable precise, visual management of the physical infrastructure of an IT park. They facilitate space management, the planning of equipment additions, and the monitoring of interventions in a datacenter.", "sections": [ { "title": "Overview", "items": [ "Racks enable precise, visual management of the physical infrastructure of an IT park. They facilitate space management, the planning of equipment additions, and the monitoring of interventions in a datacenter." ] }, { "title": "Add an item", "items": [ "You can an asset by clicking on +", "Then choose your asset in item type then Item", "Select the associated options :", "Rack", "Position", "Orientation (from rack point of view)", "Background color", "Horizontal potision (from rack point of view)", "Reserved positiion", "After clicking on + Add, the material appears in the rack at the position indicated" ] }, { "title": "Delete an item", "items": [ "To delete an item, click on the pen on the concerned item", "Click on Delete permanently" ] }, { "title": "Custom an item", "items": [ "In order for the information in the right-hand box to be filled in (weight and power), you must enter these values manually.", "In Setup > Dropdown > Models, select the type of asset you want custom", "Select the asset concerned", "Fill in the necessary information", "You can add pictures that will be visible on the rack", "If you don't add an image, you can set a color for each item you add. you can also switch between images and colors using the images button" ] }, { "title": "Power units", "items": [ "You can add PDUs from power units.", "Click on + Add", "select racked or placed at rack side", "Choose the PDU in item", "fill in the following fields", "Rack", "Position", "Orientation (front rack point of view)", "Horizontal position (form rack point of view)", "Backgroud colour", "Reversed position", "If consumption data are correctly entered, they will be fed into the power units", "To delete a PDU, click on the image of PDU :", "Click on delete permanently" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/rack_items.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/rack_items.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/rack_items.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0096", "title": "Software", "category": "assets", "tags": [ "glpi", "documentation", "assets", "softwares" ], "relatedIssuePatterns": [ "assets", "softwares" ], "summary": "This tab, named Softwares and visible in a Computer entry, allows to manage the software installed on a computer. Those software are sorted by their category and are characterized by name, version and version status.", "sections": [ { "title": "Overview", "items": [ "This tab, named Softwares and visible in a Computer entry, allows to manage the software installed on a computer. Those software are sorted by their category and are characterized by name, version and version status.", "To install a software, first select its name in the drop-down list, then its version.", "It is possible to associate a license to a software on a computer.", "To associate a license, first select the software in the drop-down list, then the wanted license.", "If the license is associated with a software that is already installed on the computer, it will be presented in the list of software.", "Otherwise it will be displayed in a separate table.", "the drop-down list enumerates the software that are available in the entity", "licenses management can be found in `Assets > Softwares`.", "See Manage software", "It is possible via mass actions to install on a computer a software selected from its license.", "Every deletion or addition of a software or a license is recorded in the history of the computer.", "If using native inventory or third-party inventory tool, the software information can be automatically imported and updated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/softwares.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/softwares.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/softwares.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0097", "title": "Virtualization", "category": "assets", "tags": [ "glpi", "documentation", "assets", "virtualization" ], "relatedIssuePatterns": [ "assets", "virtualization" ], "summary": "This tab displays the virtualization systems (virtual machines, containers, jails....) associated to a host.", "sections": [ { "title": "Overview", "items": [ "This tab displays the virtualization systems (virtual machines, containers, jails....) associated to a host.", "You can either remount the virtual machine in the assets tab or include it in the virtualization tab of the host that hosts them. To make this change, go to Administration > Inventory > Virtualization.", "The available information vary from one system to another: for a virtual machine for instance, it includes :", "Name", "Automatic Inventory", "Virtualization system", "Virtualization model", "State", "UUID", "Processors number", "Allocated memory", "As well as the name of the physical machine (the host).", "GLPI establishes the link between a host and a virtual machine based on the unique identifier (UUID). In some case, it is possible that the UUID is different inside the physical machine and the virtual machine; it is therefore impossible to make the link automatically.", "Several systems are supported, including HyperV, VMWare, VirtualBox, WSL, etc.", "The only way to link manually a virtual machine to a physical machine is to attribute the same UUID to the virtual machine declared on the host and to the virtual machine inside GLPI.", "If using native inventory or third-party inventory tool, the virtualization information can be automatically imported and updated." ] }, { "title": "Add a virtual machine", "items": [ "To add a new virtual machine, click on Add a virtual machine", "Enter the information of the new machine", "By clicking on +, you can add a new :", "Virtualization system", "Virtualization model", "You can manage these items in Setup > Dropdowns > Virtual Machines", "A machine added manually will, by default, be identified as automatic inventory: No. This information cannot be modified." ] }, { "title": "Delete a virtual machine", "items": [ "To delete a virtual, you need to click on this (on assets directly or in the virtualization tab of the host)", "Click on Put in trashbin", "If the VM was a computer in assets, click on the trashbin", "Select the checkbox", "Click on Actions", "Delete permanently (keep or remove devices as required)", "If the VM is still present on the host, it will be remounted during the next inventory. You will therefore also need to delete it from the host" ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/virtualization.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/virtualization.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/virtualization.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0098", "title": "Volumes", "category": "assets", "tags": [ "glpi", "documentation", "assets", "volumes" ], "relatedIssuePatterns": [ "assets", "volumes" ], "summary": "This tab, named Volumes and visible in a Computer entry, allows to manage the volumes attached to a computer.", "sections": [ { "title": "Overview", "items": [ "This tab, named Volumes and visible in a Computer entry, allows to manage the volumes attached to a computer.", "A volume attached to a computer is characterized by:", "name", "physical partition", "mount point", "file system", "total size", "available size", "ciphering algorithm and type", "It is possible from a Computer entry to add a volume by clicking on button `Add a volume`.", "It is possible from a Computer entry to modify an existing volume by clicking on the link under its name.", "Every deletion or addition of a volume is recorded in the history of the computer.", "If using native inventory or third-party inventory tool, the volumes information can be automatically imported and updated." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/volumes.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/tabs/volumes.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/tabs/volumes.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0099", "title": "Unmanaged assets", "category": "assets", "tags": [ "glpi", "documentation", "assets", "unmanaged-assets" ], "relatedIssuePatterns": [ "assets", "unmanaged-assets" ], "summary": "Unmanaged equipment is equipment that is not directly administered by a GLPI agent or a protocol such as SNMP, WMI, etc. Unlike managed equipment, it does not automatically report information and must be manually updated in the inventory. These devices have been detected during a network discovery and can be converted into another type of object, either manually or via SNMP feedback.", "sections": [ { "title": "Overview", "items": [ "Unmanaged equipment is equipment that is not directly administered by a GLPI agent or a protocol such as SNMP, WMI, etc. Unlike managed equipment, it does not automatically report information and must be manually updated in the inventory. These devices have been detected during a network discovery and can be converted into another type of object, either manually or via SNMP feedback.", "This will prevent it from being modified the next time the automatic inventory is uploaded.", "For more information, see lock", "In a unmanaged asset form, the following information is available:", "Name", "Location", "Manufacturer", "Serial number", "Inventory number", "SNMP Credentials", "Network", "Update source", "Approved device: Yes / No", "Status", "Technician in charge", "Alternate usernmame number", "Alternate usernmame", "Sysdescr", "User", "Comments", "IP", "Network hub: Yes/No" ] }, { "title": "Network Ports", "items": [ "This tab allows to manage the network ports attached to the item. The information that can be viewed is:", "Name", "Port number", "MTU", "Speed", "Internal status", "Last change", "Number of I/O bytes", "Number of I/O errors", "Duplex", "VLAN", "Connected to", "Connection", "Deleted" ] }, { "title": "Domains", "items": [ "You can attach Domains to the current item. Domains are also linked to other objects such as records, problems, etc." ] }, { "title": "Locks", "items": [ "You can lock/unlock the fields you wish in a GLPI object." ] }, { "title": "Import information", "items": [ "Import information is information that is uploaded and governed by equipment import rules (Administration > Rules > Rules for import and link equipments)" ] }, { "title": "Massive actions", "items": [ "This item has a specific massive action which allows it to be converted into another type of object (computer, printer, etc.).", "You can convert it manually via this massive action, or report it via SNMP, WMI, etc." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/unmanaged_assets.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/assets/unmanaged_assets.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assets/unmanaged_assets.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } }, { "id": "GLPI-DOC-0100", "title": "Appliances", "category": "management", "tags": [ "glpi", "documentation", "management", "appliance" ], "relatedIssuePatterns": [ "management", "appliance" ], "summary": "The Appliances in GLPI refer to the software and applications managed within the GLPI tool. This includes all software solutions installed on users' machines, servers and other devices within the organisation. Applications can include office applications, business software, operating systems, utilities, etc.", "sections": [ { "title": "Overview", "items": [ "The Appliances in GLPI refer to the software and applications managed within the GLPI tool. This includes all software solutions installed on users' machines, servers and other devices within the organisation. Applications can include office applications, business software, operating systems, utilities, etc." ] }, { "title": "The basics fields", "items": [ "Name", "Status", "Location", "Technician in charge", "Group in charge", "Manufacturer", "Alternate username number", "Alternate username", "Serial number", "Inventory number", "User", "Group", "Comments" ] }, { "title": "Appliance type", "items": [ "The appliance type is used to define the appliance context (VOIP, EDM, etc.). You can select the type of application from the drop-down list, or add a new one directly by clicking on the +." ] }, { "title": "Appliance environment", "items": [ "The application environment designates whether the application is in production, acceptance, pre-production, etc. This field can of course be adapted to suit your needs." ] }, { "title": "Pictures", "items": [ "You can add a picture for your appliance." ] }, { "title": "Impact Analysis", "items": [ "This can be saved and exported" ] }, { "title": "Items", "items": [ "List of all other linked GLPI Items . You can manually add an item by selecting it from the drop-down list. An appliance can also be linked to another appliance" ] }, { "title": "Contracts", "items": [ "GLPI supports contracts management , in order to manage contract types such as loan, maintenance, support…", "Contracts management allows to:", "make an inventory of all contracts related to the organization assets", "integrate contracts in GLPI financial management", "anticipate and follow contract renewal." ] }, { "title": "Documents", "items": [ "The document tab lets you link different types of file to a material (PDF, txt, png, etc.) You can attach a document already uploaded to GLPI or add a new one directly from this tab." ] }, { "title": "Management", "items": [ "this information is visible in the ‘Management’ tab on the object form." ] } ], "attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/management/appliance.rst", "source": { "project": "glpi-project/doc", "path": "source/modules/management/appliance.rst", "revision": "f868e7fa28f87789a192d891fe9783dd485c47e6", "url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/management/appliance.rst", "license": "CC BY-SA 3.0 FR", "licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en" } } ] }
{
"version": "1.0",
"generatedAt": "2026-07-22T19:06:23+00:00",
"generatedFor": "Peppermint additive GLPI knowledge expansion",
"totalDocuments": 100,
"source": {
"project": "glpi-project/doc",
"repositoryUrl": "https://github.com/glpi-project/doc",
"revision": "f868e7fa28f87789a192d891fe9783dd485c47e6",
"license": "CC BY-SA 3.0 FR",
"licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en"
},
"documents": [
{
"id": "GLPI-DOC-0001",
"title": "Defining actors and roles",
"category": "assistance",
"tags": [
"glpi",
"documentation",
"assistance",
"actors"
],
"relatedIssuePatterns": [
"assistance",
"actors"
],
"summary": "An assistance service usually defines the following roles:",
"sections": [
{
"title": "Overview",
"items": [
"An assistance service usually defines the following roles:",
"Requester : user or group of users known to GLPI and affected by the ticket;",
"Technician: ticket processing is done by a technician, by a group or by a supplier;",
"Watcher : user who can follow a ticket but without modifying it; follow-up can be done from GLPI interface or by receiving notifications.",
"Visible information and possible actions are defined by GLPI based on the user's role, which is defined in user's profile:",
"Technicians are the actors having the most complete information on a ticket and the widest possible actions",
"Requester and watcher will only view the information needed to fulfill request.",
"For multiple users or groups, only the first user or group is defined when creating the ticket, more actors are added later. A user who cannot modify actors but able to see the ticket can become a watcher.",
"When associating a new actor to a ticket, the number of tickets assigned to this actor is visible; this eases for instance task partitioning between technicians.",
"for users who are not known to GLPI, mail address can be associated to a ticket. Default choice for requester and watcher (no selected user) allows to add a mail address in these fields; for this to be available, notifications must be activated (see notification management )",
"Role attribution is done in user's authorization management (see Attribute authorizations to a user )"
]
}
],
"attribution": "Adapted from the GLPI user documentation by GLPI contributors. Licensed CC BY-SA 3.0 FR. Source: https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/actors.rst",
"source": {
"project": "glpi-project/doc",
"path": "source/modules/assistance/actors.rst",
"revision": "f868e7fa28f87789a192d891fe9783dd485c47e6",
"url": "https://github.com/glpi-project/doc/blob/f868e7fa28f87789a192d891fe9783dd485c47e6/source/modules/assistance/actors.rst",
"license": "CC BY-SA 3.0 FR",
"licenseUrl": "https://creativecommons.org/licenses/by-sa/3.0/fr/deed.en"
}
},
{
"id": "GLPI-DOC-0002",
"title": "Categories",
"category": "assistance",
"tags": [
"glpi",
"documentation",
"assistance",
"categories"
],
"relatedIssuePatterns": [
"assistance",
"categories"
],
"summary": "by selecting a parent category using in first tab the field As child of",
"sections": [
{
"title": "Overview",
"items": [
"A category can be made hierarchical:",
"by selecting a parent category using in first tab the field As child of",
"by adding a new child category in tab ITIL Categories"
]
},
{
"title": "ITIL categories",
"items": [
"ITIL categories can be managed in dropdown setup Setup > Dropdowns > Ticket Categories.",
"ITIL categories are used by Tickets, Changes and Problems.",
"A person in charge and/or a technical group can be added to this category and will then be used for notifications.",
"A knowledge base category can also be associated to this category; this will register the solution in this category of the knowledge base.",
"In this example, if you have a ticket with the category \"Hard disk failure\" which is linked to the KB category \"Failure > Computer\", when you add a solution to the ticket with \"Save to Knowledge base\" set to \"Yes\", the default category in the new Knowledge base Article form that opens will be \"Failure > Computer\".",
"A category can be invisible in simplified interface, in order to reduce list of categories for end-users. It can also be made visible or not for incidents, demands, problems or changes.",
"A template can be associated with this category and will be loaded when this category is selected in ticket. This template can be different for demands and incidents.",
"When building a helpdesk, it is important to choose carefully the list of available categories: a too large number visible by end-users will make ticket creation less easy, whereas a too small number will not allow you to correctly qualify the demand.",
"Ticket categories allow to do automatic processing when creating a ticket, for instance modify ticket attributes; see Business rules for tickets ."
]
},
{
"title": "Task categories",
"items": [
"Task categories are used to sort task in order to ease their processing or to build meaningful statistics."
]
}