What was said earlier is not correct. “Subscribers” and “users” are the same thing. Prior to phplist 3 they were called users, but now are usually referred to as subscribers, but documentation is probably still inconsistent.
People who sign-up to your phplist are registering to receive email newsletters from you, not to administer phplist itself. You create additional administrators yourself manually.
**People who sign up as subscribers cannot be converted to admins
Ok, so say I have a “user” who signs up.
I can mod phplist to then give this user “admin” privs. In fact I could mod the app to do this as part of the reg/signup process.
**Admins can’t sign themselves up (must be added by another admin)
**subadmins can have different access permissions (configured when you add them), but these permissions are not grouped into roles per se
I saw in the demo for the config section (if I recall) where there are a number of different “categories” that an admin/subadmin can be granted. Is this correct.
If phplist has different “subadmin/admin” categories, then the basic “structure” I’d need is there for me to mod the app to bend it to my will!
I could assign a user on signup/registration with a subadmin “category”/role
I could then restrict access of different menus/pages, based on the category of the user. Again, logic changes.
But I’m imagining the underlying table schema/logic structure would be adaptable to what I’m considering.