As I stated in the first post, I created a new admin user account for a developer. I did not create the user account as something else and then upgrade the account to admin later. I manually created the admin account under s2Member/Add A Member. The next day, on two different web sites I created admin accounts through both s2Member/Add A Member and Users/Add New. There is no difference between the two as they take you to the same Add New User page. All three admin accounts were created as admin, not upgraded after creation.
Later, as a test, I manually changed the admin account to a level 9 account and discovered that the account lost admin rights. I expected this behavior, but simply wanted to test if it made any difference.
If you check the Add New User page you will see that the admin user account can be registered as admin at the point of creation. It does not require a later upgrade to create an admin user. And yes, the registration notification is sent when an admin user is created. Not only is it confusing that an admin account stays at level 4, why would you do that? That’s like saying that it would make sense to classify the admin as level 2 in a 4 level configuration, or the default admin is level 2 if Pro were not used. Do you see what I mean? It does not make sense.
The only place I saw it in s2Member was the registration notification email. I first observed the issue in results provided by our custom software. Our software uses certain triggers that are generated by s2Member but does not modify s2Member in any way. I created an admin account for a developer. I did not expect the new admin account to be the recipient of level 4 characteristics in our custom software, I expected it to receive level 9 characteristics, as that would be logical, since level 9 is now the highest level.
So, are you claiming that s2Member is designed this way? If so, why is it designed this way?