---
type: concept
title: Resource Approval
tags: ["administration", "workflow", "resources", "ums", "approval", "authorization"]
related: ["ressourcenverwaltung", "ressourcen-beantragen", "ums", "fremddomain", "ressource-beantragen"]
created: 2026-06-30
updated: 2026-06-30
sources: ["output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_ressource_genehmigen.md", "output/rz_uni_greifswald_de_dienste_allgemein_ressourcen_spezialfall_fremddomain.md", "output/rz_uni_greifswald_de_dienste_allgemein_zentraler_nutzeraccount_nutzeraccount_bea.md"]
---

# Resource Approval

**Resource Approval** (also referred to as **Ressource Genehmigen**) is the administrative process by which a designated staff member, supervisor, or approver reviews and accepts or rejects requests for IT resources or accounts within the university's management systems. It serves as the necessary bridge between [[ressourcen-beantragen]] (the request) and the actual provisioning of the resource by the [[universitatsrechenzentrum-urz]].

## Approval Authority

The required approver depends on the type of resource being requested:

- **Standard Resources**: Approved by the designated resource manager or department head.
- **External Domains ([[fremddomain]])**: Must be approved specifically by an employee of the **Rektorat** or the relevant **Dekanat**. Approval by these bodies also triggers the [[universitatsrechenzentrum-urz]] to cover the domain costs.

## Workflow

### General Resource Approval
For general IT resources submitted via the [[ums]], the workflow is as follows:
1. **Notification**: When a user requests a resource and designates an approver, the approver receives an automated email notification.
2. **Review**: The approver logs into the [[ums]].
3. **Execution**: The approver navigates to **Genehmigung -> Ressourcen-Anträge** (Approval -> Resource Requests).
4. **Decision**: The approver selects the specific request to either approve or reject it.

### Account Approval Workflow
For the creation of user accounts (specifically guest accounts), the approval process is also managed through the [[ums]].

**Technical Execution:**
- Approvers are notified of new requests via email.
- To process these requests, the approver must log into the [[ums]] and follow this navigation path: **Genehmigung** $\rightarrow$ **Account-Anträge genehmigen**.
- From the resulting overview, the approver can select the specific request to either approve or reject it.

**Approver Constraints for Guest Accounts:**
To ensure accountability and identity verification, the following restrictions apply to the person designated as the approver for guest accounts:
- **Personal Identity**: The approver must provide a **personal email address**.
- **Exclusions**: 
    - **Functional Accounts**: Shared or role-based accounts cannot be used for approvals.
    - **MED Addresses**: Email addresses from the University Medicine (Universitätsmedizin) are not permitted to act as approvers in this specific workflow.