Roles & Rights
Detailed roles and responsibilities for large editorial teams, tailored to university structures.
The problem
In university installations that have grown over time, nobody knows any more who is allowed to do what. Rights are assigned individually, approvals happen by word of mouth, and errors only surface once they are live.
What the extension does
Features that really count in day-to-day university operations.
Role-based model
Predefined roles for departments, editorial team and administration — instead of individual rights.
User management
Assign roles to editors in bulk, centrally and traceably.
Approval workflow
Changes only go live after approval — with the four-eyes principle.
Area permissions
Access to page trees separated by faculty or institution.
Log
Who changed what and when — as a traceable audit log.
Rights templates
New institutions get a clean rights scheme straight away from a template.
AD connection
Roles can be derived from Active Directory or LDAP groups.
TYPO3 standard
Backend extensions follow established TYPO3 conventions.
Technical profile
What your IT team will want to know up front.
Frequently asked questions
More questions? Write to us.Yes. Each institution only gets access to its own page tree; cross-cutting rights remain reserved for the administration.
Yes. With TYPO3 workspaces, changes only go live after approval by an authorised person.
Yes. AD or LDAP groups can be mapped to editorial roles, so rights continue to be managed centrally.
Yes. A log records changes with user, time and content.