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

# User Management

Manage users and control their access to data and functionality in Struct PIM through Users, User groups, and Roles.

User Management provides the tools for managing access to Struct PIM across your organization. It brings together the settings that determine who can use the system, what data they can work with, and which functionality is available to them.

Access is managed through a combination of Users, User groups, and Roles. This structure allows administrators to organize access according to responsibility, teams, markets, or other organizational needs.

***

### What you can do with User Management

* **Manage users** by inviting users to Struct PIM and assigning them roles and user groups.
* **Control data access through user groups** by defining which language, segments, and business units users can access.
* **Define access levels** by giving users read or write access to the data available through their user groups.
* **Manage permissions** through roles that determine which actions and funtionality users can access in Struct PIM.
* **Combine access settings** by assigning users multiple roles and user groups, with their permissions and data access combined across all assignments.
* **Set deafult dashboards** for user groups to provide newly invited users with a predefined starting point in Struct PIM.

***

### User Management walkthrough

The User Management area is divided into three sections for managing users and their access.

#### Users

Manage the individual users who have access to Struct PIM and control their roles and group memberships in [Users](https://docs.struct.com/reference/user-management/users.md).

#### Roles

Define and manage the permissions users are granted, individually or combined across multiple assigned roles, in [Roles](https://docs.struct.com/reference/user-management/roles.md)

#### User groups

Define which data users can access and whether they have read or write permissions and assign default dashboards in [User groups](https://docs.struct.com/reference/user-management/user-groups.md).

***

### Related tutorials

* [**How to invite a new user to the PIM** - Add new users and give them access to the PIM.](https://docs.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-invite-a-new-user-to-the-pim.md)
* [**How to assign users roles and user groups** - Manage a user's access and permissions.](https://docs.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-assign-users-roles-and-user-groups.md)
* [**How to set up a role** - Define the permissions available to users.](https://docs.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-set-up-a-role.md)
* [**How to set up a user group** - Define the data users can access. ](https://docs.struct.com/tutorials/guides/how-to-work-with-user-management/how-to-set-up-a-user-group.md)


---

# 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.struct.com/reference/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.
