> For the complete documentation index, see [llms.txt](https://idthrivo.gitbook.io/thrivosign-remote-signing-solution/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://idthrivo.gitbook.io/thrivosign-remote-signing-solution/proof-of-concept/t-sic-mobile-app-scal2.md).

# T-SIC Mobile App - SCAL2

{% content-ref url="/pages/xNZbOgF5FMBHiLAe6HKw" %}
[Mobile App Signing](/thrivosign-remote-signing-solution/thrivosign-remote-signing-solution-t-rss-documentation/remote-signing-solution/t-sic/mobile-app-signing.md)
{% endcontent-ref %}

Outlined below are the **step-by-step procedures** for efficiently guiding through the process of using    T-SIC Mobile App: 

**Credential:** 

* **Username**: <alice@idthrivo.com>
* **Password**: Sign1234

To access the features of the SIC Mobile App, users need to log in with their credentials.

<figure><img src="/files/q5DULzkroH8HwRBtyO66" alt=""><figcaption></figcaption></figure>

When the application detects this is the first time a user logs in, it will prompt for SIC Activation. The user will receive an SMS OTP. Once the activation code is received via SMS OTP and entered into the application, the application will validate the activation code. Essentially, this is the user device binding step.

<figure><img src="/files/v9d3SawUJKeWuDzp8otn" alt=""><figcaption></figcaption></figure>

Once the activation code is validated, the application will show the home screen.

<figure><img src="/files/wJtu183EbRdJ9mP0c71Z" alt=""><figcaption></figcaption></figure>

The RA will enroll and issue a certificate to the user. Go to Certificate Management to view the certificate details and activate the certificate.

<figure><img src="/files/lswidJxxALPXMEWcCC3l" alt=""><figcaption></figcaption></figure>

On this screen, the application will display the list of certificates issued to the user.

<figure><img src="/files/gfLu34X4xkk6wut9ppFQ" alt=""><figcaption></figcaption></figure>

Users are given two options: to activate or reject the certificate. By clicking the down arrow, the details of the certificate will be displayed.

<figure><img src="/files/chESURMLjUQpS6nN25YC" alt=""><figcaption></figcaption></figure>

Users can view the details of the certificate before activating it.

<figure><img src="/files/fT8EYFf01vPYtY4VbtlY" alt=""><figcaption></figcaption></figure>

Once the certificate has been activated, the status will change from “New” to “In use”.

<figure><img src="/files/3t46UM6X4J28eHFNCJja" alt=""><figcaption></figcaption></figure>

On the SSA, user upload document to be signed.

<figure><img src="/files/EfUEeASDAc3tioYUoHMt" alt=""><figcaption></figcaption></figure>

SSA display uploaded document.

<figure><img src="/files/pI6mymlR21DiLAYHWLic" alt=""><figcaption></figcaption></figure>

User add recipient into the workflow.

<figure><img src="/files/k2fID5RWkf7jgu0olmoi" alt=""><figcaption></figcaption></figure>

User prepare document fields.

<figure><img src="/files/LF2WhmDZ9Peqt1wVP3E5" alt=""><figcaption></figcaption></figure>

Process and share document.

<figure><img src="/files/atIlyx3h3l22RKrspPlm" alt=""><figcaption></figcaption></figure>

The SSA displays pending documents to be signed.

<figure><img src="/files/kVENih9ItRYlY282WRzM" alt=""><figcaption></figcaption></figure>

Once the user signs the document, the application will send a push notification to the user's SIC Mobile App.

<figure><img src="/files/tiPiDXS9wUZnNRwWVeML" alt=""><figcaption></figcaption></figure>

Users are given two options: "Approve" or "Reject". To proceed with signing the document, users must select "Approve."

<figure><img src="/files/7msxAOuEmI1WNvSuEauU" alt=""><figcaption></figcaption></figure>

After approving the request, users have the option to view and download the signed document.

<figure><img src="/files/eQOd5Kh0nRiWClEDFWAX" alt=""><figcaption></figcaption></figure>

The SSA will display the status of the document as completed after the user approves the request.

<figure><img src="/files/CdaBrpiTo1inFQLC8heq" alt=""><figcaption></figcaption></figure>