> 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/gateway/da/getting-started/devolutions-server/gateway-ruleset-configuration-in-devolutions-server.md).

# Konfiguration af gateway-regelsæt i Devolutions Server

Konfigurer et regelsæt for Devolutions Gateway i Devolutions Server for at begrænse netværksadgang efter IP, undernet, domæne, bruger eller vault.

Begræns netværksadgang, og segmentér trafik uden at oprette en ny Gateway-instans på en anden maskine ved hjælp af Gateway-regelsæt. Regler kan konfigureres til at tillade eller afvise forbindelser efter IP-adresser, undernet, IP-intervaller eller domæner. Derudover kan sikkerhedsregler håndhæves for at tillade eller afvise adgang for bestemte brugere eller brugergrupper eller på vaultniveau. Følg trinnene nedenfor for hurtigt at konfigurere et Gateway-regelsæt i Devolutions Server:

1. Gå til ***Administration*** – ***Devolutions Gateway***.
2. Klik på ***Tilføj*** (***+***), og vælg ***Gateway-regelsæt***.
3. Vælg en ***Fysisk gateway*** på listen over gateways i Deres Devolutions Server.
4. Angiv et ***Navn*** til Gateway-regelsættet.
5. Klik på ***Gem***.


---

# 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/gateway/da/getting-started/devolutions-server/gateway-ruleset-configuration-in-devolutions-server.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.