For the most part, your role is effectively determined by your interaction with domains, and there are just two roles to apply for, the others are system assigned. In addition to roles, there is a class system.

0. ip-anonymous
   

   Basically same as ip-identified and 'essential cookies only' in common usage but acknowledges a request to remain anonymous.

1. ip-identified
   

   Monitors unauthenticated access. A slow manual path for registration from the live dev node is mostly to support professional courtesy waivers. Registration path is equivalent to social-networked.

2. social-networked
   

   A basic entitlement level associated with registration thru a 3rd party Identity Provider (IdP). Same trust level as the IdP.

3. tx-authenticated
   

   A variable privilege default automatically created by a transaction such as an in-app purchase. May be limited to a particular product space or customer service group.

4. developer
   

   A high privilege level with an engineers level of resource consumption and control.

5. operator
   

   A very high privilege level that allows control of system software.

Roles at level 3 and lower are assigned by the system. Level 3 (S, Y, and F class capitation) are normal users. Higher permission levels are associated with priced services beyond capitation. Roles below level 2 are handled as classes but level 2 is assumed to be all human individuals, potential AKPERSONs.

more on the role system used in these domains ...