> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/retail-lending/help-center/troubleshooting/user-management.md).

# User Management

Find the cause and the fix for common User Management problems.

Each item gives what you see, why it happens, and what to do.

<details>

<summary>A user sees "Login successful!" but stays on the sign-in page</summary>

**Why:** The user's only role is **Administrator**, which has no permissions until you grant them.

**What to do:** Grant permissions or assign a role they need. See [Roles](broken://pages/lwftzPHlwUChlhZeEB6T).

</details>

<details>

<summary>A user doesn't see a new application tab</summary>

**Why:** A new product's application tabs aren't visible to any role until that role has view permission for each tab and for the data behind it.

**What to do:** Grant the role view permission for each tab. See [Roles](broken://pages/lwftzPHlwUChlhZeEB6T).

</details>

<details>

<summary>The user's navigation didn't change after a role change</summary>

**Why:** The user's navigation updates when they sign in again.

**What to do:** Ask the user to sign out and sign in again. See [Module Access](broken://pages/EebOasKPKQhWq9ggrFQL).

</details>

<details>

<summary>A removed role still shows in the Roles column</summary>

**Why:** The **Roles** column updates when you reload the page.

**What to do:** Reload the page. See [Manage Users](broken://pages/f7gdPumh7eDJyAOWCy9G).

</details>

<details>

<summary>"Permission denied. You do not have access to this section."</summary>

**Why:** The user opened a page their roles don't allow, for example from a bookmark or shared link, and Retail LOS returned them to their home page.

**What to do:** Assign the role the user needs for that module. See [Module Access](broken://pages/EebOasKPKQhWq9ggrFQL).

</details>

<details>

<summary>A user was deactivated by mistake</summary>

**Why:** The confirmation is a plain browser dialog, so it's easy to select through.

**What to do:** Select **Activate** on the user's row. See [Users](broken://pages/R12dPPQIdLYNTwAjtl7j).

</details>

<details>

<summary>Applications are unworked after you deactivated someone</summary>

**Why:** The person was named on work queues.

**What to do:** Check the queues in **Manage Queues** before you deactivate someone, so their applications are picked up by someone else. See [Manage Queues](broken://pages/Z5lL0LhJf641nu5qRvHP).

</details>

<details>

<summary>Borrower isn't offered in Assign Role</summary>

**Why:** **Borrower** can be set only when a user is created.

**What to do:** Create the user with the **Borrower** role. See [Roles](broken://pages/lwftzPHlwUChlhZeEB6T).

</details>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://2966508920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff06WQMAu97E0STor0yyS%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/retail-lending/help-center/troubleshooting/user-management.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.
