Difference between revisions of "B-Op HR Hub"

Revision as of 17:19, 8 July 2023

HR Data importing is required for almost all usage cases of B-Op software, as larger companies typically have a HR system already in place.

To integrate with these HR-systems, B-Op HR Hub was created to integrate seamlessly.

Please note that this topic has to be observed closely and must be aligned with the b-op data ownership and privacy principles.

There exists a HR Hub core service, installed

Data acquisition plugins - They are used to accumulate hr base date from multiple systems into one data pool hosted in the HR hub. They are stored locally and encrypted (storage security)
1. simultaneously (Graph API, Hr-System, AD, picture source, csv, .... )
2. invoking each other (pictures imported by another plugin)
Transport
1. with filtering on row level (e.g. External users are not relevant to Klesy)
2. with filtering on column level (e.g. BKC is non relevant to Print environments)
Import plugins - They are used to import the transported HR information into target digitals:

@@ Line 14: / Line 14: @@
 ##with filtering on column level (e.g. BKC is non relevant to Print environments)
 # '''Import plugins''' - They are used to import the transported HR information into target digitals:
-== Privacy regulation and deletion service (RPDS) ==
-Each digital must individually define its privacy settings, which can be accomplished through the [[App:HR and 3rd party privacy settings App|HR and 3rd party privacy settings App]]. These settings determine:
-* how '''HR Hub''' is importing and distributing information
-* how the [[Dev:Privacy regulation and deletion service (RPDS)|privacy regulation and deletion service (RPDS)]] is performing data deletion and anonymization
 == Related articles ==