> For the complete documentation index, see [llms.txt](https://docs.tiun.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiun.io/reference/customer-account/devices-and-connected-apps.md).

# Devices and connected apps

In the [account portal](https://docs.tiun.io/reference/customer-account/overview.md), customers can see where their tiun account is signed in and sign out remotely. There are two places for this: **Linked devices** for the tiun account itself, and **Connected apps** for the businesses they've signed into.

***

## Connected apps

The **Connected apps** section lists every app and website the customer has signed into with tiun, yours included. Opening one shows the **devices** the customer is signed in on there, with each device's last activity.

From there the customer can:

* **Log out** one device.
* **Log out on all devices** for that app or website.

tiun also emails the customer each time their account is used to sign in at a business, so they can spot a sign-in they don't recognize and end it here.

***

## Linked devices

Under **Settings → Linked devices**, the customer sees the devices signed in to the portal itself, split into the current device and other devices. They can log out one device, or **log out on all devices** at once. When logging out of all devices, they can also choose **Include connected apps**, which signs them out of every app and website they've used tiun with.

Logging out of all devices can take up to 10 minutes.

***

## What happens in your app

When a customer signs out of your app from the portal, the session on that device ends. The SDK finds out the **next time the page loads**:

* The session can't be restored, so `userChange` fires with `event: 'init'` and `isAuthenticated: false`, and `tiun.user` is `null`.
* A page that's already open stays signed in until it's reloaded.

If you already handle a signed-out user on page load, there's nothing to add. See [Authentication / How it works](https://docs.tiun.io/reference/authentication/how-it-works.md#session-persistence) and [Protecting content](https://docs.tiun.io/reference/authentication/protecting-content.md).

If you have a backend that verifies users server-side, it sees the change once the session has ended: verification returns `isAuthenticated: false`. See [verifying authentication server-side](https://docs.tiun.io/guides/authentication/verify-server-side.md).

Signing out doesn't change what the customer has paid for. Their subscriptions and purchases are still there the next time they sign in, and `productAccess` comes back with them.

***

## Where to go next

* [Overview](https://docs.tiun.io/reference/customer-account/overview.md) — what else customers can do in the portal.
* [Authentication / How it works](https://docs.tiun.io/reference/authentication/how-it-works.md) — sign-in, session restore, and logout.


---

# 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.tiun.io/reference/customer-account/devices-and-connected-apps.md?ask=<question>&goal=<user_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.
