> 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-groups/security-group-aliases.md).
# Security Group Aliases
In the Aliases Tab you can set Aliases to easily synchronise Security Groups and Business Units
To reach the Aliases Tab open a **Security Group** drawer and go to to the 2nd tab.
Here you will see a list of the Aliases created and if you have admin permissions you will be able to create more by clicking on the + symbol.
Once an Alias is created you will be able to assign Business Units to it using the drop down menu for each Alias when you click on the "Business Unit" input field.\
Once selected a drop down menu with all the existing business units will open where you can select one or many business units.\
Once selected the business units will appear each time this Alias is selected
Now each time this **Security Group** is assigned to a user (both new and existing) the business units attached to the Alias for this security group will be assigned to that user.\
\
Please note the user must log out and log back in for the change to take effect in their browser.
---
# 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-groups/security-group-aliases.md?ask=&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.
