...
i) you cannot add TC users to any 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. Alternately, otherwise we would remove that user from the 1st account, then add them to the 2nd ( though this will not be possible if they have submitted SDRs)
AMO and AOC accounts have completely the same functionality.
The only difference in an AME account is AME accounts have the same funtionality as AME/AMO, the only difference being that AME submissions get forwarded to regional Team Lead PMI’s (allocated on TR86) as opposed to a company specific PMI dictacted dictated by the NACIS views.
Example of TR86 data
...
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 - where that number is active) and is not currently in use by another 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 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).
All non-submitters are encouraged to use the public search facility rather than setting up an account.
Public search facility
...
Consequently, the requestor will often attempt to register several times, and will create 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. (checks for occurences of M79.organization_id and M79.sequence_nbr on M72)
...
A TC account is defined as a Userid that exists on TC_directory – and/or - has an email address domain of 'tc.gc.ca' (This domain is subject to change in the future, due to Shared Services domain issues)
...
All TC employee Userids are already resident in CAWIS. If a person is not found, that userid will likely be imported during the next overnight sync, provided that TC Access control has allocated the account.(Procedure: CLEANSE_CAWIS_DATA) Another way to verify a new user, is to put the person’s name in the Send-to field of an email, then click “check names”.
Note: PMI registration has been deactivated on the external website, and replaced with a contact email for access. These Userid’s have usually already been setup before the requestor asks for access.
Adding a TC user to an internal organization
Step 1 - go into edit mode on an existing user for that organization
...
Step 2 - Search for the user surname you’re looking for, select them then fill out the form
...