> For the complete documentation index, see [llms.txt](https://docs.dataloy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/setup/security-roles/maintain-security-roles.md).

# Maintain Security Roles

When you have located a **Security Role**, click it and the details will show in a drawer on the right hand side. Details can be maintained directly in the fields/tree.

* By clicking the primary action icon <img src="https://content.gitbook.com/content/zjy4yJFZRJooU1EGrLs5/blobs/aRkkVhmYWgPS2BQVWwKO/Screenshot%202020-04-06%20at%2014.02.28.png" alt="" data-size="original"> it is possible to make a copy of the selected **Security Role**, a \
  modal will open where you enter the name of the copy.<br>
* By clicking the secondary actions icon (icon = 3 dots) additional actions may be possible.
  * Edit Security Role Name
  * Delete Security Role
* The drawer tabs include **Groups** and **Data Controls**, which contain lists showing the **Security Groups** and **Data Controls** the opened **Security Role** are related to.

{% hint style="info" %}
Filters can be used to locate permissions in the tree.
{% endhint %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dataloy.com/release-8.31/voyage-management-system/step-by-step-guides/setup/security-roles/maintain-security-roles.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 `build a script that syncs our docs to a CMS` 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.
