---
type: concept
title: TYPO3 Access Workflow
tags: [provisioning, access-control, workflow]
related: [typo3-backend, ums, ressourcenverwaltung]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_typo3_webseiten_typo3_zugang_zum_redakti.md"]
---

# TYPO3 Access Workflow

The **TYPO3 Access Workflow** is the specific implementation of [[ressourcenverwaltung]] for the university's CMS. It distinguishes between the *technical ability to log in* (the resource) and the *authority to edit content* (the permissions).

## The Five-Step Process
1. **UMS Request**: User requests the "Zugang zum TYPO3-Backend" resource.
2. **Departmental Approval**: A supervisor approves the request.
3. **Webmaster Activation**: The URZ Webmaster activates the resource.
4. **User Initialization**: The user logs in via [[shibboleth]] to create the backend account.
5. **Permission Mapping**: The Webmaster assigns specific Page IDs (PIDs) or URLs to the account.

## Key Distinctions
- **Resource vs. Permission**: Having the UMS resource allows a user to enter the backend, but they will see an "empty backend" until the Webmaster manually assigns permissions.
- **Initial vs. Extended Access**: The UMS is used only for the initial "gate" to the system. Subsequent changes to the scope of editable pages are handled via email to the Webmaster.
