Employees, departments, teams, and contact groups

asset administrators can use the workspaces listed below to manage and organize user records a high level overview of these workspaces is provided here; for more details, see the ivanti neurons for itsm online help at help ivanti com https //www ivanti com/support/product documentation for details about assigning user roles, see user roles docid\ ppu9pnhhmi85adryx5dhj employee workspace this workspace displays a list of all the employees in your database—employees are both users of itam and customers who can request assets employees are typically imported from your primary employee data source, though you can manually add them here as well all employee records must include details such as name, email address, login id, org unit, and primary team the employee belongs to as you add data to the database, you'll also be able to view an employee's assigned user roles and contact groups, associated assets, allocated software entitlements, and more from this workspace asset administrators can edit and create new employee records using this workspace; all other user roles have read only access as best practice, we recommend that you define your employee departments and teams (in the department and teams workspaces respectively) before importing or manually adding employees to the database department workspace this workspace enables you to define departments within an organization, such as it or marketing, which can be used to categorize employees in the employee workspace teams workspace this workspace enables you to create and manage teams of employees a team is a more specific category than the department an employee belongs to—individual employees can be on more than one team, and teams can be created from employees working in separate departments teams are responsible for adding items to the product catalog and fulfilling asset requests asset requests must be associated with at least one team, because request assignments are given to teams and use team email rather than individual email an asset request may also include one or more tasks that another team needs to complete before the request can be fulfilled contact group workspace you can configure itam to use an approval process for setting up contracts, purchase orders, and product catalog items in doing so, the process advances only after the majority of a group of approvers has approved the item use the contact group workspace to add employees to a contact group that's responsible for advancing an approval process after a person is added to a group, they'll receive an email when a process has begun that requires their approval managers, supervisors, and senior personnel are common members of contact groups if your database is integrated with ivanti neurons for itsm, the list view will show contact groups for both products the contact groups specific to itam are purchase order approvers – for details about configuring, see procurement docid 5y6ijsgccb zcicdylsm product catalog item approvers – for details about configuring, see product catalog docid\ mg4kcnt2jlkxs4b04gjeh note that if a non standard catalog request is made by a user, the approval process must go through members of this group if a standard request is made, approval is based on the manager associated with the person requesting the item after configuring a contact group, you have the option of deactivating it at any time to deactivate a contact group open the contact group workspace from the list view, click the group you want to make inactive change the status to inactive and click save click list view to return to the main list