> For the complete documentation index, see [llms.txt](https://docs.fogwing.io/fogwing-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fogwing.io/fogwing-platform/profile-management/logout.md).

# Logout

Follow these steps to Logout of Fogwing IIoT Platform.

## Logout When Needed !

When you are done working on the Fogwing IIoT Platform, its best you stay connected and Logout. Logging out is simple and an easy process. 

To Logout:

1. As the primary step, Login to your Fogwing IIoT Platform account.
2. The Home page will appear soon after Login.
3. Towards the top right corner of the screen, You will a button with 'Profile name' and User icon will be found. Click the same. A Drop box will appear.
4. From the drop box, click the option that reads 'Logout'.
5. Once the Logout button is clicked, the user will be logged out and will land on the Login page.


---

# 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.fogwing.io/fogwing-platform/profile-management/logout.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.