> For the complete documentation index, see [llms.txt](https://docs.noports.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.noports.com/usage/policy-service.md).

# Policy Service

This page describes using the policy service

### Policy Service Status

The Policy Service must remain running at all times to listen for incoming requests from daemons querying the policy server.

### Policy Roles

In the context of the Policy Service, a **role** defines a set of access permissions that determine which Atsigns can interact with specific devices or groups of devices through NoPorts.

When creating a role you will need to enter the following information:

|                    |                                                                                                                               |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------- |
| **Name**           | The role's name                                                                                                               |
| **Description**    | The role's description                                                                                                        |
| **Device Atsigns** | The device Atsign(s) to which the policy role will be applied                                                                 |
| **Devices**        | The device name(s) associated with the device Atsign along with the local ports that NoPorts has permitted for secure access  |
| **Device Groups**  | The device name(s) associated with a group of devices along with the local ports that NoPorts has permitted for secure access |
| **User Atsigns**   | The Atsigns that will have access to the devices and/or device groups                                                         |

After a role is created and saved, the Atsigns listed in the User Atsigns section will be able to connect to the designated ports and interact with the specified devices using the assigned device Atsigns.

If using device groups, be sure the specify the device group name when running the NoPorts Daemon on your device. For example:

```bash
./sshnpd -a @<YOUR DEVICE ATSIGN> -p @<YOUR POLICY ATSIGN> --device-group <DEVICE GROUP>
```


---

# 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.noports.com/usage/policy-service.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.