| CPC H04L 63/104 (2013.01) [H04L 67/535 (2022.05)] | 20 Claims |

|
1. A tracking system, the tracking system comprising:
at least one processor operatively connected to a memory;
an authorization component, executed by the at least one processor, configured to:
accept definitions of user authorization objects for a set of verified users, each user authorization object including a linkage between a user role and a data element specifying an authorization attribute;
a restriction component, executed by the at least one processor, configured to:
identify, based on the user authorization objects, from the set of verified users, a first subset of the verified users having a first user role, the first user role having a linkage with a first authorization attribute specifying an access to generate tracking objects each including one or more progression metrics; and
responsive to user input in a user interface and based on the user authorization objects, restrict access to functions executed on the system that are configured to generate the tracking objects to the first subset of the verified users having the first user role having the linkage with the first authorization attribute specifying the access to generate tracking objects;
a listing component, executed by the at least one processor, configured to:
responsive to user input in the user interface by the first subset of the verified users having the first user role to which access is restricted, generate tracking objects each including one or more progression metrics; and
list tracking objects each including one or more progression metrics at a listing index accessible by a second subset of the verified users having a second user role, the second user role having a linkage with a second authorization attribute specifying an access to enroll with tracking objects; and
a tracking component, executed by the at least one processor, configured to:
update tracking objects based on collection of metric values of respective verified users of the second subset of the verified users having the second user role for respective progression metrics.
|