You define users by assigning a unique ID in User Maintenance (36.3.1). Each program is always passed the user’s ID, any group names associated with the user for the current domain, and access information associated with the user. After you create the ID for a user, you specify other identifying information and preferences.
Note: User IDs cannot be blank, or the same value as a user group name.
User Maintenance (36.3.1)
To log in, each user must specify a unique user ID and the associated password. Other user data is referenced throughout the system and may be required for reasons other than security.
User profiles apply to all domains in the system. However, profiles include several generalized codes that are domain specific such as access location and user type. To prevent validation errors, you should ensure that these codes exist in all domains.
Note: Batch processes must be assigned a valid user ID.
Once a user has accessed the system, the ID cannot be deleted. Instead, you can make users inactive. If an ID has never been used for log-in, you can delete it, if necessary. This lets you correct any errors made during initial setup.
Note: This restriction ensures a complete audit trail of users who have accessed the system.