> For the complete documentation index, see [llms.txt](https://docs.giize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giize.com/ticket-dashboard-en/user-guide/dang-nhap.md).

# Logging in to the systems

The dashboard needs your login sessions to read data. There are three separate sessions that expire independently of each other — logging in to SDP does not refresh your IT Portal session.

| Session         | Used for                               | How to log in                            | Validity                                       |
| --------------- | -------------------------------------- | ---------------------------------------- | ---------------------------------------------- |
| SDP             | Overview, My SDP Tickets, Ticket Tools | account + approve a number on your phone | a few weeks                                    |
| TS Jira and ACL | OpenVPN                                | PIN + OTP code                           | TS a few days, ACL until the session is closed |
| IT Portal       | My Portal, Portal Tools                | PIN + OTP code                           | a few days                                     |

You do not need to log in ahead of time. Just go to the page you need and the dashboard will tell you when a session is missing.

## Logging in to SDP

Go to **Overview** or **My SDP Tickets**, then press **Đăng nhập SDP** (Log in to SDP) on the status bar at the top.

1. Enter your internal username (the part before the `@` in your company email)
2. Enter your password
3. A number appears on screen — open Microsoft Authenticator on your phone and select that exact number

Step 3 can take 30–60 seconds. Do not close the tab while you wait.

{% hint style="info" %}
Your password is not saved to disk. Only the login session is stored so you do not have to start over next time.
{% endhint %}

Once done, the status bar turns green and shows the number of tickets that were synced.

## Logging in to TS Jira and ACL for OpenVPN

Go to **My SDP Tickets → OpenVPN**. This page needs two different sessions:

| Button        | Which session it gets | When you need it                            |
| ------------- | --------------------- | ------------------------------------------- |
| **Fetch TS**  | TS Jira               | when you need to read or create TS tickets  |
| **Check ACL** | ACL                   | when you need to check a user's existing IP |

Both ask for a **PIN + OTP code** in a single field: type the PIN immediately followed by the 6-digit OTP from Google Authenticator, with no space.

The **Cookies** label next to the buttons shows which session is still valid:

![OpenVPN page](/files/dkAGg8U8znrns709reca)

If both sessions are still valid, go straight to **Quick refresh** — you do not need to do the steps one by one.

## Logging in to IT Portal

Go to **My Portal → Portal Tools** and enter your **PIN + OTP** when prompted.

Next time you return, the dashboard uses the saved session. The status dot next to the page title tells you whether the session is still valid.

## When you need to log in again

There is no fixed schedule. The signs to watch for:

* the status bar turns red and says you need to log in again
* the numbers on Overview stay frozen even after you press refresh
* the OpenVPN page reports `need_login`
* Portal Tools cannot fetch orders

The fix is the same in every case: log in again to whichever system reported the error. See also [What to do when something goes wrong](/ticket-dashboard-en/user-guide/faq.md).