> 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 that defines what they can view, edit, or configure.

**User groups** bundle permissions: assign a role 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**, 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.datalogz.io/guides/organizational-setup/user-onboarding-guide/users-and-user-groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.