System Administrator – This role represents the system and is responsible for maintaining the application environment coherently, It can access and configure the LMS’ services, as well as control possible subordinate users and their privileges.
User –This role is the generic human role. It represents any registered or non-registered users, and LMS users.
Visitor –The Visitor represents a school or a student from a school which might be an LMS user, but is not yet authenticated in the system. This user is only allowed to register/authenticate and to perform other basic interactions with the system.
Institution User –The Institution User role represents the subordinate users (Teacher, Master Teacher, Students) of an organization. These users can only access a subgroup of the services the institution has subscribed to in LMS’ platform. Note that Institutions Admins also exist to administer institution service subscriptions and maintenance, but based on the context can function as an Institution user role.
CSR –This actor represents a Customer Service Representative who is able to administer the LMS platform and its intricacies.
Customer/Client Institution –This actor represents the subscriber to LMS’ platform. It will usually be the system administrator for a particular application instance.
Change of Services –The system administrator can change the information related to a service’s instance and access and manage its set of subscriptions and subscribers.
Change Level Of Service –Customers can alter their service’s Level Of Service on the run. For this, they may have to pay for the changes.
Consult Subscription –A system administrator can access a running service’s subscription and renew or cancel it, change its Level Of Service, consult other subscription information or manage the set of users with service permissions.
Access Service –Any subscriber (Customer or Institution User) can access a service, on the condition that it has permission to access that service.
Terminate Subscription –The LMS’ Admin will be able terminate subscriptions when the conditions for that are met.
This ends the Part 2 of our series, in the next Part we will look at an important challenge of turning free subscription based account holders to paid-subscription based accounts and we will also ponder over how to generate in-app engagement that can lead to increased user retention. We will also be listing the steps to implement the strategy for both of these goals.