...
A TC-employee’s CAWIS userid ALWAYS matches their network login. These TC userids are auto-synced against TC-_directory_client every night so that the keeping contact and addressing info remains up to date. (or, for example if an entire branch, like Aircraft Certification, changes locale, we don’t need to update addressing on dozens of individual Userids)
A "new" WSDRS userid New WSDRS userids for TC personnel should NEVER be manually created in CAWIS/WSDRS - the a Userid will be deactivated overnight if it has a "tc.gc.ca" email domain and is not found on TC directory.
For example. when assigning a new user to the TC-Flight services organization (50049450), you need to select the person from the existing users already in CAWIS, not create a new id. (note: Flight Services always required requires special case handling for its accounts)
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 an the account.(Procedure: CLEANSE_CAWIS_DATA) Another way to test for thisverify a new user, is to put the person’s name in the Send-to field of an email, then click “check names”.
EXTERNAL WSDRS Organization configuration requirements
For any External WSDRS organization, the user at sequence number 1 needs to be:
- set to "Active"
- set to "Manager"
- allocated as a generic userid (if possible, example: AIRCAN1 ) so that new personnel can be swapped in and out of this userid, when people retire, and the new manager needs to resume the business of the previous person.