---
title: "Using Linked Groups"
slug: "using-base-groups"
description: "This document explains how to use and assign Linked Groups in Decisions. Linked Groups are used as a way to associate multiple groups with one another. The association can be used to assign a task or allow access to certain folders to multiple groups via a shared association, with or without being in the same initial group. "
updated: 2026-07-22T21:22:29Z
published: 2026-07-22T21:22:29Z
canonical: "documentation.decisions.com/using-base-groups"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Linked Groups

## Overview

When creating or editing a group, the **Linked Groups** setting is an option to associate one group with another. All of the accounts in the selected Linked Group will have access to the same Assignments and objects as the group it is being associated with.

Centralized Account Management with Deployment Server

If your environment is connected to the Deployment Server, manage centralized user accounts from the Deployment Server. Administrators can create accounts on the Deployment Server and assign them to connected environments to keep access consistent across Development, QA, and other connected servers.

After an account is assigned to an environment, the account information synchronizes with that environment. Permissions specific to projects, folders, or other security settings must still be configured directly in the target environment where the user will work.

For more information, see: [Managing Accounts with the Deployment Server](https://documentation.decisions.com/docs/managing-accounts-with-the-deployment-server)

---

## Example

This example consists of an account named developer@example.com that will belong to the **Developer Team** and the **Designers** groups and an account named sales@example.com that only belongs to the Designer group. In the example, the Developer Team will be linked to the Designers Group to allow all accounts within the Designers Group to see and access a folder named Dev Apps.

1. Create an account named "dev@example.com" and add it to a group called **Developer Team** and **Designers**.
2. Create another account named "sales@example.com" and add it to the Designers group.
3. Create a new Designer Project at the Root and name it "Dev Apps".
4. Once the Designer Project is created, right-click on the name and navigate to **Manage > Manage Permissions**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783016557635.png)
5. In the **Manage Folder Permissions** window under the GROUPS category, click ADD. Click PICK to select the **Developer Team** group. Under PERMISSIONS, select all the permissions for the Developer Team to have access to. Select OK and then SAVE PERMISSIONS.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783016656533.png)
6. In Decisions Studio, navigate to **System > Security > Groups.** Right-click on the Developer Team group and select **Edit Group**.
7. Select the **Specify Linked Groups** checkbox. Under the LINKED GROUPS category, click ADD.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783016675988.png)
8. Click PICK and select Designers. Click PICK and click OK. Click SAVE.
9. When the an account from the Developer Team group logs into the Decisions environment, it is now able to access the project folder as well. If an assignment were sent to the Developer Team, the Designers group would also receive the Assignment. All of the permissions, access, and task actions associated with one group will remain present in the other while the groups are linked.