User File Import for NIAM
Clients should create separate sets of files for active users in the following format. This is a description of the fields available on the User Definition form that have to do with NIAM.
If you wish to enable myAvatar users for NIAM, please refer to that article for process steps.
Note:
- There is one set of files for UAT users per root system code.
- There is one set of files for PROD users per root system code.
Note: The files should be a tab-delimited text file with each user on a separate row with no header row.
- Fields 1 through 4, 6 and 7 should be populated for each user and the values set to match what they currently are in myAvatar. If the field is not populated in myAvatar, do not populate that field in the file.
- Fields 5, 8, and 9 must be populated as indicated in the Note column to enable NIAM. These values will not match what is currently in myAvatar.
| Order | Field | Note |
|---|---|---|
| 1 | User ID | myAvatar user ID (existing) |
| 2 | User Description | |
| 3 | User Role(s) | This is an ampersand delimited string of the user's roles (SYSTEM.radplus_users table stores the user roles as an ampersand delimited string). Remove leading and trailing ampersands. Example: &Role1&Role2& would become Role1&Role2 |
| 4 | Staff Member ID | If no value in myAvatar, leave unpopulated |
| 5 | Associate User to Network ID through Avatar Identity Manager |
To enable NIAM (EID), this should be set to 2.
|
| 6 | Organization Code | organizations_code If no value in myAvatar, leave unpopulated |
| 7 | Organization Facilities | org_facilities_colde If no value in myAvatar, leave unpopulated |
| 8 | Use External Login | To enable NIAM (EID), this should be set to Y. To remove NIAM, this should be set to N. |
| 9 | External Login ID (Azure userID) |
Identity Provider - Client Azure userID To enable NIAM, this should be set to the users External Login ID from the IdP |
- ► See Also