Abstract: Embodiments of the present invention teach use of a single-platform with its own authentication-process (i.e., its own “single-platform-authentication-process” or its own selection of secure single-platform-authentication-processes), but that may allow third party service provider companies (Organizations) that want to offer/provide service(s) on the single-platform, to still utilize their own authentication-processes, i.e., to still utilize the given Organization's own “organization-specific-authentication-process,” at least once in the initial user onboarding process, and thereafter to rely upon the common authentication-processes of the single-platform; which then permits a multitude of services, including the possibility of diverse and different services to be deployed from the single-platform.

Abstract: Embodiments of the present invention teach use of a single-platform with its own authentication-process (i.e., its own “single-platform-authentication-process” or its own selection of secure single-platform-authentication-processes), but that may allow third party service provider companies (Organizations) that want to offer/provide service(s) on the single-platform, to still utilize their own authentication-processes, i.e., to still utilize the given Organization's own “organization-specific-authentication-process,” at least once in the initial user onboarding process, and thereafter to rely upon the common authentication-processes of the single-platform; which then permits a multitude of services, including the possibility of diverse and different services to be deployed from the single-platform.