Please i have extracted list of users from T24 Production environment, and i noted that there are some users IDs have their naming convention not equal our standard naming convention mechanism. So please i need your support to understand what is the T24 Build in accounts and which account are recommended to be disable after the implementation and which should kept enable, and regrading the build in account that should kept enable it's applicable to change their password or it will affect the service.

The following ID:
ATM.USER01
AUTHORISER
BASEAUTH
BASEUSER
DCUSER
DMUSER
GTUSER
SRINI.1
SRINI.2
SYS.ATMUSER
SYS.COBUSER
SYS.TSMUSER

Based on your provided list and compare on our environment. there is some user that is not listed also.
I suggest you look on attributes which has value of SUPER.USER

Also can your please clear your requirements??

Thanks for your replay . all mentioned IDs above have super. User privilege and based on our interview with CIO we were informed that such users are build-in users which is system accounts. So my question is can we disable these IDs or even resetting their password and if yes,,, is this will affect any service?

Hi
users that are used in TSA.SERVICE records should present in F.USER. Their END.DATE.PROFILE can even be in the past - our services do work this way.