...
i) you cannot add TC users to a External SDR organization ( the only exception is Flight services )
ii) you cannot add a specific user to more than 1 SDR organization. You will frequently need to create a 2nd userid for some people for a 2nd use (an example being an AMO account and a TCH account for a single individual).
Alternately, we could possibly remove that user from the 1st account, then add them to the 2nd ( though this is not possible if they have submitted SDRs)
...
An AME/AMO/AOC user is sent a confirmation email upon successful self-registration provided that the license number they provide, is verifiable on CAWIS tables AMO_info/AOC_info/AME_info (which are refreshed daily - DBMS jobs 181,182,183) The AME/AMO/AOC number MUST be “active” and not currently in allocated to an existing user.
All Other (types 4,5,6) registration types are sent to the WSDRS email inbox for management review. No confirmation email is sent to the requestor. This is handled manually by SDR manager decision.
Sample email received by WSDRS inbox for “other” type registrant
...
(Examples of Other-type registrations: media outlets, Flight Training Units, Law offices, research companies, insurance companies, foreign operators with no AOC number, Aircraft owners mistaking this subsystem for a place to enter an AAIR after an EDM).
...
Frequently, the requestor will attempt to register several times, and will create creating multiple redundant Userids in the process. When this occurs, simply change the password to "DELETE" on any duplicate accounts, and the overnight job will perform an auto-deletion, if no reports have been submitted from these accounts. (It checks for occurrences of M79.organization_id and M79.sequence_nbr tied to records on M72)
...
TC userids are auto-synced against TC_directory_client every night, keeping contact and addressing info up to date. (for example if an entire branch, like Aircraft Certification, changes locale, we don’t need to update addressing on dozens of individual Userids)
...