With the LDAP connection, authentication can be carried out against existing LDAP-enabled systems (Active Directory, OpenLDAP, eDirectory, etc.) i-doit can be configured in context in such a way that an Active Directory user is automatically logged in to it (single sign on).
The LDAP connection is also important for the documentation of the allocations of contacts to documented objects in the CMDB. So, for example, all employees in the Active Directory can be assigned to your workstations or computers and the admins provided with all necessary contact details to hand in order to inform the user about upcoming changes or outages.
Each i-doit user has a separate area in which to store frequently used objects as favourites as well as search favourites. The my-doit area also makes a filter available with which to display within the CMDB only objects with particular CMDB statuses. When using the workflow module, you'll also find your personal workflow.
i-doit is delivered in English and German. i-doit is developed using language constants so it is easy to create your own language file for your language.
i-doit is web-based
The disadvantage of conventional IT documentation is that files are either stored locally or can only ever be opened by one user with write access. i-doit is web-based, making it OS-independent and centrally accessible to all. i-doit is compatible with all major web browsers (see system requirements).
The object lists are customisable and user-defined. Simply adding or deleting attributes can configure the columns of the table lists of the object configured to your liking. Only the object properties that are of interest to you appear in the tables.
Logbook with comment function
The logbook in i-doit logs all changes that were made to an object. When connected to an (optional) commenting function, these log entries can also be provided with additional information, for example, to record the reason for a change. In addition, the logbook serves as an archive for various extensions in which the status or events from a live operation can be stored. This functionality provides the logbook with a central modification status and archive for the IT components deployed.
For example, the results data from the Nagios® and RT pairings can be recorded in the i-doit logbook. If, for example, a system fails, this information is recorded - obviously associated with the correct object - in the i-doit logbook. Thereby the life cycle of an object can be comprehensively logged.
Instead of deleting objects in i-doit, they may be put into an archived state for the time being. All properties, including relationships with other objects, are in this way saved. This feature protects objects from accidental deletion. Additionally, this function has a particular relevance in connection with i-doit's rights system. This ensures that not all users are able to remove an object from the database, with this right being reserved for administrators only.
With an i-doit hosting license, you can create multiple clients. These have separate databases and function as independent instances of i-doit. This way you can set up access for various clients in an installation without running the risk that information intended for one client is received by another. This gives both you and your clients the confidence that they can only see the data that they are authorised to do so. If you are interested in the multi-client capability of i-doit, please select the hosting license.