...
The first thing many of you might ask yourself is, “yes, HR Accounts are always human people but what about the downstream Account Stores' technical or non-human accounts? Do I need a Person object for these?” These accounts are referred to as “Non-Person Accounts” and defined as “Any account not specifically assigned to a person, such as accounts used for devices, services, and servers.”
Source: Bago (Editor) E. & Glazer I., (2021) “Introduction to Identity - Part 1: Admin-time (v2)”, IDPro Body of Knowledge 1(5).
A valid question is whether you need to create Person objects for these types of Accounts. The answer is not always clear-cut but rather a maybe or sometimes. You are not required to create a Person object for non-human person accounts you wish you manage directly in EmpowerID (create, edit add/remove from groups, reset the password, disable, etc.)
Below is a list of common use cases for which you would want to create a Person object to own the non-human person Account.
Deciding When You Need a Person Object
...