> For the complete documentation index, see [llms.txt](https://compassly.gitbook.io/compassly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://compassly.gitbook.io/compassly-docs/core-modules/shifts/shift-management/view-resource-allocation-panel.md).

# View the Resource Allocation Panel

**Page type:** Task Guide\
**Status:** Draft\
**Owner:** Compassly Documentation Team\
**Last verified:** 2026-07-08\
**Audience:** Super Admin, Admin, Supervisor, Clinician, Basic

## What This Section Covers

This material covers how to review scheduled and published hours across a team using the Resource Allocation Panel, and how to download that data as a spreadsheet.

## Before You Start

* You must have permission "Manage shifts and notes".
* The panel is only available in ***Day***, ***Week***, or ***Month*** view — it's not available in ***Table*** view.
* What you see is scoped to your own access: if your role doesn't include seeing all team members' shifts, you'll only see your own hours.

## Where To Start

1. Sign in to Compassly.
2. In the left navigation menu, select ***Shifts***.
3. In the left navigation menu, select ***Shift Management*** from the dropdown menu under ***Shifts***.
4. Make sure you're in ***Day***, ***Week***, or ***Month*** view.
5. Click ***Resource Allocation*** in the page header.

## Available Actions

1. **Switch between breakdown by Team Member or by Clients.**
   * Use the ***Breakdown by*** toggle at the top of the panel. Team Member is selected by default.
2. **Read the hours columns.**
   * Each row shows ***All Hours*** (every shift regardless of status), ***Published Hours*** (shifts that are Published, signed or not), and ***Unpublished Hours*** (Unpublished and Template-status shifts). A **Template** row at the bottom of each table covers hours from Template-status shifts that have no team member or client assigned yet — it has no Published Hours value, shown as a dash, since a shift with nobody assigned can't be published.
3. **Understand how weeks are grouped.**
   * In ***Day*** or ***Week*** view, the panel shows one table for the calendar week (Monday through Sunday) containing whatever day or week you're currently viewing. In ***Month*** view, it shows one collapsible table per calendar week that touches the selected month — including partial weeks that spill into the previous or next month — with the first week expanded by default.
4. **Download the data.**
   * Click ***Download*** above any table to export that specific week's data as a CSV file.

## Role Differences

* ***Super Admin / Admin / Supervisor:*** Can see allocation data for team members and clients they're connected to — see [Connections](/compassly-docs/administration/system-settings/connections.md) for how Team and Location connections determine who that includes.
* ***Clinician / Basic:*** Only sees their own hours.

## Summary Of Section

**Upon reviewing this material, you should be able to:**

* Open the Resource Allocation Panel and read its hours breakdown
* Switch between a Team Member and Clients view
* Download a week's allocation data as a CSV

## Related Guides

* [View My Assigned Shifts](/compassly-docs/core-modules/shifts/shift-management/view-my-shifts.md)
* [Connections](/compassly-docs/administration/system-settings/connections.md)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://compassly.gitbook.io/compassly-docs/core-modules/shifts/shift-management/view-resource-allocation-panel.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.