> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/knowledge-base/how-to-articles/enforce-domain-containers.md).

# Enforce domain containers

Enforce domain containers in Devolutions Server by reviewing configured organizational units so all users and groups keep proper access and permissions.

Domain containers are enforced in Devolutions Server. In earlier versions, as long as the administration credentials had rights to other organizational units (OUs) of the domain, users and user groups could still be used even if they were outside those containers. That is not the case anymore.

Ensure that all users and user groups can be used:

1. Log in to your Devolutions Server web interface using and administrator account.
2. Go to ***Administration – Server settings – Authentication – Domains***.
3. Click on ***Edit*** next to your domain.
4. Go to the ***Advanced settings***.
5. In ***Domain containers***, check if you have any OUs selected. If you have some configured, please ensure that all the users and user groups are included here, or else the users and groups outside of those containers will not be able to connect or have the proper permissions. You could also remove those domain container restrictions if your Active Directory is not large.
6. Click ***OK*** then ***Update*** to save your changes.


---

# 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.devolutions.net/server/knowledge-base/how-to-articles/enforce-domain-containers.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.