Introduction
Core identity types describe a specific user type. These user types, for example Internal Employee and External Employee, differ in various characteristics such as the list of managed attributes or in the configured processes such as entry or exit process. However, another very central feature is also the authorization concept. If these differ from each other, a clear and simple separation can be achieved by mapping two different core identity types.
There are also is also one predefined Core Identity Types used by the system called Service Accounts. All internal service users used to run the CoreOne Suite are of this type. So it’s advised to not change or modify this Core Identity Type.
Parameter
The following parameters can be managed when creating or mutating a core identity type.
Parameter | Data type | Mandatory field | Example value | Description |
|---|---|---|---|---|
Name | string |
| External person | Describes the core identity type |
Employment necessary | boolean |
|
| Describes whether an employment must be created to create a core identity of this type or not. For internal persons, for example, employment is always mandatory, whereas it is not necessary for a customer. |
Attribut Mapping
The attributes mapping of the core identity type defines which attributes are available. For example, internal employees can consist of a first name, a last name and an employee number. In the case of customers, on the other hand, the delivery address may be required in addition to the first and last name.
When adding an attribute to the core identity type attribute mapping, it is also possible to define whether this attribute should be visible to the user in the CoreOne Suite portal and whether the user is allowed to mutate it there independently in the sense of a self-service.
Duty attributes
It is mandatory to fill in the following attributes.
Parameter | Data type | Example value | Description |
|---|---|---|---|
Display name | string | First name + last name | Without a display name, the object cannot be included in the lists. |
Workflows
Without a display name, the object cannot be included in the lists.
Workflow | Description | Input | Example Workflows |
|---|---|---|---|
Core Identity Added | Executed when a new core identity of this type is captured | Core Identity ID | Informing the supervisor about the entry |
Core Identity Updated | Executed when an existing core identity is mutated | Core Identity ID Changes (All changed attributes) | Informing people about a name change |
Core Identity Deactivated | Executed when a core identity is deactivated | Core Identity ID | Information email to the supervisor |
Core Identity Employment Changed | Will be executed when
| Core Identity ID Employment ID Mutation type (Add, Update, Delete) Changes (All changed attributes) | Updating the main setting in conversion systems |
Roles
Fixed roles can be stored on the core identity types. Adding a role ensures that each core identity of this core identity type receives the corresponding role.