The problem: distributed identity landscape
A typical university runs in parallel:
- The central Microsoft Active Directory for staff and lecturers (central IT)
- Institute- or faculty-owned ADs (grown historically, often with different naming conventions)
- Entra ID (Azure AD) for M365 cloud users and students with campus IT accounts
- Separate student directories from the university administration software (SIS, SAP SLCM, CAMPUSonline etc.)
- Guest and partner identities for exchange programmes
Classic print-management systems expect one directory. The result: duplicate registrations, inconsistencies, manual maintenance, frustrated IT.
The Docuflair solution: multi-source sync with rule engine
- Parallel synchronisation: any number of sources simultaneously — AD, Entra ID, LDAP, CSV imports
- Role merging: a user in multiple sources (e.g. Prof. + admin assistant) is consolidated, roles combined by priority rule
- Quota inheritance: budgets can be defined per source, group or user — including overrides
- Schedule-based sync: lecture period vs. holidays — different rules automatically active
- Delta updates: only changes are transferred, no full-sync load on the AD side
Real example: A university with 18,000 students and 1,400 staff previously ran 4 parallel print-quota systems because the directories didn't match. With Docuflair multi-sync, this was consolidated into one configuration — operational burden reduced by ~60%.