Table of Contents

Identity life cycle (ILC)

It is a contractual relationship that defines the link between an identity and a tree structure. Also, a contractual relationship plays a significant part in assigning a role to an identity. Every identity has at least one contractual relationship (CR), as a (manually assigned or automatic) role is always assigned to a contractual relationship, not directly to an identity.

Default settings

  1. a default contractual relationship is established automatically once an identity has been created
  2. provided a default element of the organizational structure is pre-configured, an identity is placed in this position within the structure when creating a default contractual relationship
  3. if there is no selected default element of the structure, the identity is "placed" in a position titled "Default" WITHOUT being included in the organizational structure.

Search managers by CR

Managers can be looked up through:

HR processes: End of contracts, and invalid contracts

HR processes depend on the state of a contractual relationship and its validity.

Prime contract position

A contractual relationship can be flagged as "main". There can be more than one CR flagged as main, or none at all.

States of a contract

Contracts can be:

  1. valid
  2. valid but “EXCLUDED”, provided the 'validFrom'' and ''validTill'' attributes are filled. Roles assigned to this contract are not removed - accounts on target systems remain intact. Roles assigned to this contract are not added to a logged identity
  3.  invalid or with the ''DISABLED'' attribute
  4. in a "null" state, if no values are entered in the ''validFrom'' and ''validTill'' attributes 

TERMINATION

INVALID CONTRACTS

DISABLED IDENTITY AND REACTIVATION

CONTRACTS WITH TIME SLICES

These HR automatic processes can be configured in two ways:

- the process is executed as soon as an identity’s contract is changed (active operation)
- long running tasks are scheduled, mainly over night. So while the contract change is saved, the respective HR processes are executed separately

Other contractual positions

Other contractual positions which can be set are used just for the assignment of automatic roles by the tree structure.
Note: the filtering and evaluating of managers and subordinates through other contractual positions is not supported.

Roles, organizations, and contracts

Linking a role to the organizational structure

Everyone authorized to edit a role can assign the role to a component of any organizational structure. Such an action, of assigning/removing a role to a structural component, is subject to the same approval as when an ordinary user is to be assigned a role. Once the approval is granted, this amounts to a sort of "pre-approval" for all the users incorporated within the organizational structure. From then on, assigning a role to a user does not require a special approval (it had been approved for the entire organizational unit in which a user is situated).

Displaying information about automatically assigned roles

The information about the roles linked to the organizational structure are displayed in these sections:

Audit

All changes regarding roles coupled with organizational structures are audited. The log provides this information: