> For the complete documentation index, see [llms.txt](https://docs.videc.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.videc.de/june5-3.7/en/webanwendung/benutzerverwaltung/verwendung-der-windows-sicherheit.md).

# Using Windows Security

For Windows security to work in JUNE5, a tenant must first be created in the JUNE5 web application. The name of the tenant must be identical to the Windows domain name. Proceed according to chapter [Tenants](/june5-3.7/en/webanwendung/benutzerverwaltung/rollenbeschreibung/mandant.md) and create a tenant with a name that matches the configured Windows domain name (see [Windows Security](/june5-3.7/en/konfigurator/windows-sicherheit.md)).

#### Example:

Windows computer name (Windows domain name) = *GLT*

Tenant name in JUNE5 = *GLT*

![In the image above you can see an example configuration. It is important that the names of the JUNE5 permission groups exactly match the names of the Windows user groups.](/files/Ei9tw3WVdwlw73FYhFMh)

Now the desired Windows user groups must be configured in the JUNE5 web application. Create JUNE5 permission groups (see [Permission Groups](/june5-3.7/en/webanwendung/benutzerverwaltung/rollenbeschreibung/berechtigungsgruppen.md)) with names identical to the Windows user groups.

{% hint style="info" %}

* If the user is deleted in AD, then AD authentication will fail and the user will have no access in JUNE5.
* If the user is disabled in AD, then AD authentication will fail and the user will have no access in JUNE5.
* A local JUNE5 user must be used for administration.
* If the username can be authenticated against AD during login in JUNE5, then this user is logged in to JUNE5. However, this user can only see objects in JUNE5 if they have been given appropriate rights via the user group.
* Only users of one tenant can be authenticated against the Windows domain.
* For using Windows security, only single-tenant mode is recommended.
  {% endhint %}

Object rights are managed on the JUNE5 permission groups. After that, you can log in to JUNE5 with your Windows user data.

Now it is possible to log in with Windows login data in the web application.

Under the subchapter [Use Case](/june5-3.7/en/webanwendung/benutzerverwaltung/verwendung-der-windows-sicherheit/anwendungsfall.md) you will find an exemplary use case about security settings in single-tenant mode.

![In the image above you can see an example configuration. It is important that the names of the JUNE5 permission groups exactly match the names of the Windows user groups.](/files/ystGQ04nm4WZCZvxf0dO)


---

# 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:

```
GET https://docs.videc.de/june5-3.7/en/webanwendung/benutzerverwaltung/verwendung-der-windows-sicherheit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.