HEAT uses two customer types, enabling a flexible user management interface. At this time, these types can not be created, modified, or deleted. These types are defined as:
- Employee: A user that is independent of any specific business object. Its unique field is LoginID. Employees are stored and authenticated by their username and password. Employees can log into the system and can be linked to and from other objects. Employees can be internal or external users, depending on your configuration.
- ExternalContact: A contact that is independent of any specific business object. Its unique field is email address. External contact user passwords are not stored in the database. External contacts cannot log into the system, but can be referenced by other objects. For example, an external contact named "Vendor" who reports an incident can be referenced within the incident object (ie. CreatedBy).
This structure enables more complex security and access control scenarios:
- Self-service access for external users.
- Service Desk Analysts can create an incident or service request on behalf of an external user or entity.
- Greater flexibility to model new types of identities and contacts.
- Separation of identity, contact and organization concepts.
- Visibility and access to business objects in security scopes that encompass hierarchical and horizontal relationships between entities linked to the service delivery.