Update AVS User Update Prozedur

FRADrive-Übersicht/Schnittstellenbeschreibungen/AVS-VSM/AVS-User-Update-Prozedur.md

@@ -87,3 +87,25 @@ flowchart TD;
 ★: Conditional update: each individual field is only updated if its actual value is identical to previous avs value and it is changed in new avs data. This means that any edited field is no longer updated automatically, unless AVS later delivers a value that happens to be identical value to the edited values.
 
 *Note:* Within this entire process supervision is only changed if UserSupervisorCompany is equal to Old AVS Company or empty and UserSupervisorReason "company default" or empty. Note the **consequence** that Supervisionships having no annotations will eventually be deleted.
+
+## Superior / Vorgesetzte
+
+`AVSFirmInfo` may deliver an Email `avsFirmEMailSuperior`. Using FRADrive DB or else LDAP, we try to associate this Email with a `UserId` (possibly created from LDAP). This user then becomes an irregular Supervisor to all company associates with reason 'Vorgesetzter'.
+
+* Rules for Superiors:
+   - Superiors do not become Company-Default-Supervisors automatically
+   - Superiors become irregular supervisors without rerouting, existing supervisions are not changed
+   - Superiors become company users at equal-to-max priority, if not already
+* For each AVN User update:
+   - if superior change for unchanged company:
+     all company supervisions with remark "Vorgesetzter" are removed
+     create admin problem that notifies about superior change 
+     (special if new superior could not be created)
+   - all company associates are irregularly supervised by the new superior with remark "Vorgesetzer"
+* Open Questions:
+   - company had superior, but no longer: just remove superior-supervisions, do not report admin problem?
+   - Problem: superior changed, but we first encounter this through a user changing company. 
+     Change is not detected at this point, old superiors remain until an old company associate is updated too
+
+
+