> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/access/failed-logins.md).

# Failed Logins

*Failed logins* is an administrative tool providing an overview of login attempts that were not successful. To invoke it, first log in as a user with administrative privileges and then go to **Settings** > *Access management* > **Failed logins**. Example report is given in Figure 1.

![Figure 1. Failed logins report listing the time of the login attempt, the display name that was used, and the reason for the login failure](https://1384254481-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJVEESmJAPppJ3ijFq5aR%2Fuploads%2Fgit-blob-c8bc7fa3fe64eab9a5b9d63829cce46bca6e8a7d%2FFailed_Logins.png?alt=media)

Each row of the table is a single failed login attempt; the time is given in the first column, the display name that was typed in on the login screen in the second column, and the reason for the failure in the third column. Possible reasons are: *Invalid credentials*, *No concurrent license available*, and *Limited to administration*.

## Additional Assistance

If you need additional assistance, please visit [our support page](http://www.partek.com/support) to submit a help ticket or find phone numbers for regional support.


---

# 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://help.bioinsight.illumina.com/partek/partek-flow/user-manual/settings/access/failed-logins.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.