---
title: "Managing Decision Release Using Population Permissions"
slug: "managing-decision-release-using-population-permissions"
updated: 2026-04-07T01:03:23Z
published: 2026-04-07T01:03:23Z
canonical: "knowledge.technolutions.net/managing-decision-release-using-population-permissions"
---

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

# Managing Decision Release Using Population Permissions

When the Release Decisions permission is granted in conjunction with a population assignment, users will only see application records within that population when navigating records in Release Decisions. For example, population-based permissions can be used to restrict visibility so that administrators in the Psychology department view only applications associated with Psychology programs.

### Assigning Population-Based Permissions

To grant a user access to records enrolled in a population, assign the user the population with **Population Permissions**.

Upon navigating to Decision Release, the user will see application records for applicants enrolled in the granted population.

1. Click **Database** on the Slate navigation bar. The **Database** page appears.
2. In the **Users & Access** section, select **User Permissions**. The **Active Users** summary page appears with a list of current active user accounts.
3. Click the desired user account from the list. The user’s account summary page appears.
4. Click **Edit User**. A popup appears, displaying the account settings.
5. Click the **Populations** tab.
6. Click **Insert Population**. An **Edit Population** popup appears.
7. Select the appropriate application population from the **Population** list.
8. Select the **Release Decisions** checkbox in the **Permissions** section.
9. Click **Save**.

> **Can I assign a role with a population permission?**
> 
> Yes. When granting a population permission with a role, grant the role on the **Populations** tab - *DO NOT* grant the role on the **Roles** tab. The user will inherit all permissions granted by the role, but will inherit the population-capable permissions *ONLY* for the selected population.