Enrollment

Owned by Richard Potter (Unlicensed)
Oct 26, 2020
2 min read

In order for users to have an identity in the MTOA platform (the ability to create and access their own private requests), they must be enrolled in your service. Depending on the design, flow, and requirements of your service, you may want to have users pre-enrolled before they access the service, or they can self-enroll when they access the service.

1. If identity verification is not required prior to making a service request (or isn't required at all):

Configuration Requirements for Self-Enrollment

  1. The service application needs to be set-up so that any user with a myTC Account can initiate a service request

    • Developers note: The enrollment API needs to be called every time a user accesses the service to ensure enrollment.

  2. A flag must be set in the MTOA DB for MTOA Online Service to make sure the service card is visible

    • Contact the myTC Account team when you begin service setup to set the flag

Two-step Enrollment Process (auto grant)

  1. User completes their first service request

  2. Upon completion, the system enrolls the user in the service request application
    (Optional: You can create a service or process that allows the user to self-enroll that is separate from the service request application)

2. If identity verification is required prior to the request for service:

Pre-Enrollment

  1. User identities are verified by the program which includes a trusted email address

  2. Contact the myTC Account team and provide trusted user details and the service they need access for

  3. An account is set-up with a PIN and an email template is provided with an enrollment link

  4. An email is sent to user

  5. The user clicks on the link with the key, and is prompted to create a GC Key. If they do not have one, the system verifies that the PIN pairs them to their myTC Account which already has permission set for the specified service

Manual Review Enrollment

  1. One Service is setup as request enrollment

  2. The line of business application retrieves the submission and the Program reviews and verifies identity

  3. On approval, system calls Enrollment API to enroll the user in to the Service Request Service

Shared Secret Enrollment

  1. One service is setup as request enrollment

  2. A line of business application reviews the request and compares values within the request (shared secret) to data that currently exists at TC to auto verify the identity

  3. If match then application calls Enrollment API to enroll the user into the service