Organization Hierarchy
  • 31 May 2024
  • 4 Minutes to read
  • Contributors
  • Dark
    Light

Organization Hierarchy

  • Dark
    Light

Article summary

Caption
Name
Requirement
Type
Description
End Timeend_timerecommended:ref:`timestamp_t <timestamp_t>`| Derived from OCSF User.end_time.
 User.end_time: The end time of when a particular state of the user was valid. Using the ``start_time`` and ``end_time`` together bound the time when a particular user state was valid. If there is no ``end_time`` it tells the analyst that this is the current state of the user as DataBee understands it. There will ever only be a single user for which the ``end_time`` is ``null``.
Ididrequired:ref:`integer_t <integer_t>`| CDPs generated Id of the organization hierarchy.
Managerlevel_1optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_10optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_11optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_12optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_13optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_14optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_15optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_16optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_17optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_18optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_19optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_2optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_20optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_3optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_4optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_5optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_6optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_7optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_8optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Managerlevel_9optional:ref:`string_t <string_t>`| Derived from OCSF User.manager.
 User.manager: The user's manager. This helps in understanding an org hierarchy. This should only ever be populated once in an event. I.e. there should not be a manager's manager in an event.
Record Created Atrecord_created_atrequired:ref:`timestamp_t <timestamp_t>`| CDPs generated timestamp when record was created.
Record Updated Atrecord_updated_atrequired:ref:`timestamp_t <timestamp_t>`| CDPs generated timestamp when record was last updated.
Start Timestart_timerequired:ref:`timestamp_t <timestamp_t>`| Derived from OCSF User.start_time.
 User.start_time: The start time when a particular state of the user became valid
IDuser_idrequired:ref:`integer_t <integer_t>`| Derived from OCSF User.id.
 User.id: The unique identifier used by DataBee for a specific user. This will be logged as ``user_id`` in activity tables to link to a particular user in this table. This field should not be mapped manually as the DataBee product populates this field itself.

Was this article helpful?

What's Next
Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence