> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/system-administration/deployment-manager/deployment-manager-prerequisites-and-roles.md).
# Deployment Manager Prerequisites and Roles
### Prerequisites
To use the Deployment Manager, your LogicNets installation must specifically include it. It is an optional, add-on component of the Shared Workspaces license. Once Deployment Manager is part of your build installation, navigate to the *Access Management* package on your dashboard to configure user access.
### User Deployment Manager Access
As with other applications, for someone to use the Deployment Manager you must give them access by adding them to an existing group that has access to the application or by creating a custom group, configuring it, and adding the user to it as a member.
When Deployment Manager is added to your installation, the system automatically includes a group called *system.deployment-managers*, which is configured with the appropriate roles. The easiest way to give a user access to the Deployment Manager is to make them a member of that group.
### Configure Group Roles
To configure a group role, you can either create a custom group and make it a member of the existing *system.deployment-managers* role with access to the Deployment Manager, or you can add the Deployment Manager as a package in the custom role you created and configured.
* If you create a custom group--for example, one for use with IdP access--you can add that custom group to the *system.deployment-managers* group as a **member**. This ensures that the group includes the relevant roles. To do this, go to your custom group and use the option highlighted with *1* in the image below.
* OR, to configure the custom group manually, do the following
* Add *DeploymentManager* to the **Packages on dashboard** in your custom group. See 2 in the image below.
* Assign the following specific categories and roles to your group manually, as identified in the image below in *3*.
| Category | Role | Note |
| ---------------------- | ----------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| *DeploymentManager* | admin or
view\_deployment
| Use the *view\_deployment* role for any user group that needs to see the versions of installed packages and where they are installed. This group cannot create or modify deployment sets. It cannot add or remove deployment configurations from instances. |
| *ManageInstanceWebAPI* | *admin* | |
| *RegistryAPI* | *read* | |
| *RegistryAPI* | *write* | |
| *RepositoryAPI* | *publish-all* | |
### Configure Workspace Roles
In the *Workspace roles* section of the group configuration page, identified in the image below with *4*, assign the workspaces to which the deployment managers have access. Typically, this is your primary editorial workspace. If you use Shared Workspaces, however, this will likely be the Master workspace that contains all of your projects.
| Workspace | Role |
| ----------------- | -------------------- |
| *\[All Relevant]* | *remote read-modify* |
---
# 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://community-test.logicnets.com/release-9/platform-documentation/system-administration/deployment-manager/deployment-manager-prerequisites-and-roles.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 `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.