---
type: concept
title: Resource Calendar
tags: [groupware, scheduling, resource-management]
related: [groupware, ums, ressource-beantragen]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_groupware_module_kalender_ressourcen.md"]
---

# Resource Calendar

A **Resource Calendar** is a specialized calendar within the [[groupware]] platform/system used to manage the booking and availability of physical or virtual resources, such as shared university assets (e.g., meeting rooms, technical equipment).

## Booking Workflow
Users can view available resources in the "Resources" section of the calendar module. The booking process follows a request-and-approval logic:

1. **Reservation**: 
   - Create a standard appointment.
   - Navigate to the **Resources** tab in the appointment settings and select the desired resource.
2. **Availability Check**: The system automatically checks for basic availability upon saving.
3. **Pending State**: The reservation is created but awaits confirmation from the resource administrator. This is indicated by the color **red**.
4. **Confirmation**: The resource administrator reviews the request. Once approved, the booking turns **green**.
5. **Rejection**: If the administrator denies/rejects the request, the resource is automatically released for that time slot.

## Provisioning and Administration
Resource calendars are not created automatically and are managed as specific IT resources:

1. **Request**: A request must be submitted via the [[ums]] (Account Management system) using the [[ressource-beantragen]] process.
2. **Setup**: The [[universitatsrechenzentrum-urz]] creates the technical resource calendar and assigns administrative rights to the requester.
3. **Configuration and Management**: The designated resource administrator is responsible for defining all further permissions, access rights, and properties of the calendar.

## Integration
Resource calendars are integrated into the broader [[ressource-beantragen]] workflow, where they are categorized as `groupware_res` requests within the UMS.