---
type: entity
title: Funktionsaccount
tags: [account, identity-management, accounts, shared-access, ums, permissions, role-based-access]
related: [zentraler-nutzeraccount, ums, ressource-beantragen, groupware, alternativer-webserver, ressourcenverantwortliche, 2-factor-authentication]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_support_dokumentation_anleitungen_informationssammlung.md", "output/rz_uni_greifswald_de_support_dokumentation_anleitungen_informationssammlung_funk.md", "output/rz_uni_greifswald_de_support_faq_groupware.md", "output/rz_uni_greifswald_de_support_faq_zwei_faktor_authentifizierung_2fa.md"]
---

# Funktionsaccount

A **Funktionsaccount** (Functional Account) is a specialized, role-based user account provided by the URZ for non-personal institutional purposes. Unlike the [[zentraler-nutzeraccount]] or other personal accounts, which are tied to a specific individual, a functional account is designed to be used collaboratively by multiple employees or even external persons.

These accounts are typically used for shared responsibilities, such as managing a departmental email address or a specific institutional function, and are highlighted in end-user training and support documentation to ensure management according to university security and administrative policies. According to the newly generated version, its security settings are managed by a designated responsible person.

## Provisioning
Functional accounts are not created as standard user accounts but are treated as IT resources. They must be requested via the [[ums]] using the following navigation path:
`Meine Ressourcen` $\rightarrow$ `Ressource beantragen` $\rightarrow$ `Functional Account`.

## Primary Use Cases
- **Collaborative Email**: Establishing a central email address managed by a team. The account can be:
    - Integrated into a standard [[mozilla-thunderbird]] or [[microsoft-outlook]] client.
    - Shared internally via the [[groupware]] platform.
- **External Maintenance**: Providing external entities access to the [[alternativer-webserver]] for technical maintenance. In this case, the UMS request must explicitly mention the target server in the description field.

## 2FA Management and Access Sharing
Two-Factor Authentication (2FA) for a functional account is managed by the [[ressourcenverantwortliche]] via the **UMS**:
`My Resources` $\rightarrow$ `Resources` $\rightarrow$ `Change 2FA`.

Since functional accounts are often used by multiple people, there are three primary methods for sharing access while maintaining 2FA security:
1. **Groupware Delegation**: The responsible person shares the account via the Groupware "share account" feature.
2. **Secret Distribution**: The responsible person provides the TOTP QR code or secret string to authorized users. To maintain security, this should be done via **Nextcloud** or a **USB stick**, and never via email.
3. **Responsibility Transfer**: The user is added as an additional responsible person for the resource via a formal change request in the UMS.

## Groupware Restrictions
Unlike personalized accounts, functional accounts have severely restricted access to the [[groupware]] suite. They are limited to the following modules:
- **E-Mail**
- **Adressbuch** (Address Book)

Access to all other Groupware modules (such as Calendar or File Storage) requires a personalized account.

## Support
Support for functional accounts is provided by the URZ via:
- The [[groupware]] ticket system.
- The URZ hotline (extension 1420).