In the past (FTH version 2 and before), the usage model that the system was designed to work with was one where the Admin did all the admin work in the platform and was the "superuser". The Admin was presumed to make most of the decisions about how the system would be configured.
Over time, we have come to realize that that early usage model really did not work well as more people became comfortable using the system and it gained wider acceptance. So we have kind of evolved to a point where multiple people (e.g. officer roles) can work on different aspects of the system in a more distributed sense, and the Admin can be more of a supervisory role that grants access to different parts of the system. In addition, it is no longer the case that the admin can unilaterally make decisions about what member info is included and not included... members have more power to decide that based on the permissions that they grant via their member profile.
Last edit: 2 years 5 months ago by SteveTheTechie.
The topic has been locked.