> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/tcs-client/getting-started/using-the-tcs-home-page.md).
# Using the TCS Home Page
What you'll find on the TCS home page, and how sessions work.
{% hint style="info" %}
**Use this when** you've logged in to TCS and want to know your way around the home page.
{% endhint %}
When you log in, you arrive at the TCS home page.
## What's on the home page
* **News** — useful information from Verifone is published on the front page.
* **Overview** — see your payment transactions for the **last 7 days**.
* **Switch company** — if your account is linked to more than one company, switch between them in the top-right corner.
## Sessions and security
* Your session lasts **15 minutes**. You can see the time remaining in the top bar. TCS logs you out automatically after 15 minutes if you're not active.
* Click **Log out** to end your session.
* For security, TCS reminds you to change your password **every 90 days** — see [How to Change Your Password](/support-nordics/tcs-client/getting-started/how-to-change-your-password.md).
Keywords
Also called: home page, start page, overview, dashboard, session timeout. Search terms: home page, overview, 7 days, switch company, session, timeout, log out.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.verifone.com/support-nordics/tcs-client/getting-started/using-the-tcs-home-page.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
