Different Types of Assets/Configuration Items in Freshservice

The CMDB/Asset Management Module in Freshservice shows you a complete list of all the assets and configuration items that have been linked within your IT service desk. By default, Freshservice comes with a set of asset/CI types that cover all the essentials for a typical IT service desk. This includes hardware items like laptops, workstations, network routers, etc. and software assets like operating systems.

Here’s a complete list of the default asset/CI types in Freshservice:

• Cloud
• AWS (EC2, RDS, EBS)
• Hardware
• Computer
• Desktop
• Laptop
• Server
• Unix Server
• Aix Server (Solaris Server, Windows Server)
• Storage (Disk)
• Data Center (Rack, UPS)
• Mobile Devices (Mobile, Tablet)
• Monitor
• Printer
• Projector
• Scanner
• Router
• Switch
• Access Point
• Firewall
• Other Devices
• Software
• Applications
• Database
• MySQL
• MSSQL
• Operating System
• Microsoft
• Linux
• Mac OS X
• Web Server
• IIS
• Apache
• Network
• Services
• IT Service
• Email Service
• Backup Service
• Hosting Service
• Business Service
• Sales Service
• Support Service
• Consumable
• Document
• Others

In case the default categories don’t fit your purpose, you can add additional asset/CI types or edit the existing ones from the Admin Settings page. 

Note: The default assets or configuration items cannot be deleted.

A quick guide to adding a new asset/CI type to Freshservice:

1. Login to Freshservice as an Account Admin.
   
   
2. Go to Admin > Asset Management > Asset Types and Fields. If your account has more than one workspace, navigate to Admin > Global Settings > Asset Management > Asset Types and Fields.
   
   
   
   
3. Click on the New Asset Type button on the top-right
   
   
4. Enter a name and description for the asset/CI.
   
   
5. Choose a parent category for the asset/CI if applicable.
   
   
6. Click on the Save button to finish adding the asset.
   
   

Note: Utilize Existing Asset Types: Leverage the out-of-the-box default asset types provided by the system. This ensures compatibility with existing features and minimizes the risk of data inconsistencies.

Hierarchy within Existing Asset Types: Instead of creating custom hierarchies, explore the option of organizing assets under the child of existing asset types. This maintains a logical structure without sacrificing system functionality.

Eg: Instead of creating Hardware < Netbook< Computer,

It’s advisable to create Hardware < Computer < Netbook