> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/signing-in.md).

# Signing in and access

Nobody can sign in, one person cannot, or someone is in but cannot see what they should.

The commonest thing a help desk hears, and the symptoms overlap — a refused password and a search tier that has gone read-only look identical to the person reporting them. Work from what they see.

* [An end user sees an error on the login page, in SelfService, or during SSO](/troubleshooting/signing-in/selfservice-and-login-errors.md) — the message-to-cause reference, and the place to start for anything a user can quote
* [Everyone gets "Invalid login/password", including accounts known to be correct](/troubleshooting/signing-in/elasticsearch-readonly-state.md) — the search tier has gone read-only
* [An "Access Forbidden" error with every service healthy](/troubleshooting/signing-in/access-forbidden.md)
* [A backend exception when running the authentication manager](/troubleshooting/signing-in/auth-manager.md) — the entitlements graph cannot be read
* [The sysadmin account is locked on a new installation](/troubleshooting/signing-in/unlocksysadmin.md)
* [An error when sending an activation link](/troubleshooting/signing-in/activationlink.md)
* [Resetting every password after the encryption key is lost](/troubleshooting/signing-in/resetting_passwords.md)
* [A user cannot see their own username in SelfService](/troubleshooting/signing-in/username_in_selfservice.md)

{% hint style="info" %}
**For one named user who cannot sign in**, [A user cannot sign in](/administration-guide/security/cannot-sign-in.md) in the admin guide triages by what they see, including MFA and password policy.
{% endhint %}


---

# 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.openiam.com/troubleshooting/signing-in.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.