> For the complete documentation index, see [llms.txt](https://docs.fact-finder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fact-finder.com/integration/generic-integration-topics/user-management.md).

# User management

Manage users, groups, roles, and authentication for controlled access to FactFinder features.

### Overview

User Management lets you assign precise permissions to individual users. For example, you can limit users to specific channels or let them manage only certain configurations. This permission model is based on roles that grant access to specific modules. Roles can be assigned directly to users or indirectly through groups. Groups make it easier to assign complex role sets in bulk.

If you use the web service connection, supply authentication data with each call. With other methods, authorization can be disabled. Only do that if FactFinder runs on a server that is not accessible from the internet.

### Basic Authentication

To use Basic Authentication, the `Authorization` header must contain the word `Basic`, followed by a space and the Base64-encoded string `username:password`.

A header using the credentials `factfinder / pw` looks like this:

```language-plaintext
Authorization: Basic ZmFjdGZpbmRlcjpwdw==
```

`ZmFjdGZpbmRlcjpwdw==` being the Base64 representation of `factfinder:pw`.


---

# 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.fact-finder.com/integration/generic-integration-topics/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.
