> For the complete documentation index, see [llms.txt](https://docs.datalogz.io/guides/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datalogz.io/guides/organizational-setup/user-onboarding-guide/users-and-user-groups.md).

# Users and User Groups

In **Users and User Groups** you manage who can sign in to Datalogz Control Tower and what they are allowed to do.

**Users** are the individuals with access. Each user holds a [role](/guides/organizational-setup/user-onboarding-guide/available-roles.md) that defines what they can view, edit, or configure.

**User groups** bundle permissions: assign a [role](/guides/organizational-setup/user-onboarding-guide/available-roles.md) to a group once and every member inherits it. This keeps permissions consistent and saves you from managing roles user by user.

**Recommended approach:**

1. Create user groups that mirror your teams or departments (for example, Finance Analysts or Marketing Ops).
2. Assign the appropriate role to each group.
3. Invite users and add them to their groups. You can wait until your Teams setup is finished before inviting users.

To invite someone, go to **Settings > Users**, click **Invite Users**, and assign their role, groups, and teams. Invitations are sent by email.


---

# 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.datalogz.io/guides/organizational-setup/user-onboarding-guide/users-and-user-groups.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.