Most customer have users of Authentication Manager authentication in an external LDAP identity source, like Active Directory or Open LDAP. So you add users there, and you 'see' them in AM through a mapping in the Operations Console. See the KB, Knowledge base article - How to create an external LDAP identity source in RSA Authentication Manager 8.1 SP1 or later
But some customers manually create (or use AMBA bulk Admin tool) to create users in the internal AM database.
There are also special case user accounts to manage AM, via the Security Console https://<AM_server_FQDN>:7004/console-ims - those users are either in LDAP or in the internal database, but they need an Admin Role to manage.
Or Operation Console users - one was created during the initial AM system deployment, other admins can be created / managed in Security Console - Administration - Manage OC Administrators
Finally there are users who can SSH into the AM appliance Linux, or logon through the console, to do some very specific and potentially dangerous things, from restarting AM services (instead of a full reboot from the Ops Console) to performing some type of database 'surgery' on the internal database.
Could you clarify which user account you are referring to ?
Most customer have users of Authentication Manager authentication in an external LDAP identity source, like Active Directory or Open LDAP. So you add users there, and you 'see' them in AM through a mapping in the Operations Console. See the KB, Knowledge base article - How to create an external LDAP identity source in RSA Authentication Manager 8.1 SP1 or later
https://community.rsa.com/s/article/How-to-create-an-external-LDAP-identity-source-in-RSA-Authentication-Manager-8-1-SP1-or-later
But some customers manually create (or use AMBA bulk Admin tool) to create users in the internal AM database.
There are also special case user accounts to manage AM, via the Security Console https://<AM_server_FQDN>:7004/console-ims - those users are either in LDAP or in the internal database, but they need an Admin Role to manage.
Or Operation Console users - one was created during the initial AM system deployment, other admins can be created / managed in Security Console - Administration - Manage OC Administrators
Finally there are users who can SSH into the AM appliance Linux, or logon through the console, to do some very specific and potentially dangerous things, from restarting AM services (instead of a full reboot from the Ops Console) to performing some type of database 'surgery' on the internal database.