Institutional sign-in
Lecturers, students and administrators use the same institutional account on the web panel and in the mobile app. The password stays with the university’s identity system; role and scope decide who sees what.
Short answer
People sign in to DAS only through the university’s identity system: SAML single sign-on or LDAP / Active Directory. DAS stores no passwords and has no self-registration; accounts belong to people imported from the SIS. System administrators, student affairs, system observers and mobile administrators take a second verification step. Every user sees only what their role and scope allow.
Identity
The password stays with the university
The same institutional account works on the web panel and in the mobile app. The password is checked by the university’s identity service at every sign-in and is never stored in DAS; password changes also happen on the university’s account page.
- No self-registration; accounts come from the SIS import
- Accounts missing from the SIS, deactivated or locked cannot sign in
- 10 failed attempts in 15 minutes lock the account for a while
Second step
Administrator sign-in takes a second step
System administrators, student affairs, system observers and mobile administrators verify their identity once more before the admin screens open. The step uses the institution’s SSO verification or a 6-digit code sent by e-mail; lecturers and students sign in directly with their institutional account.
- Hard-to-undo actions need a separate e-mail code tied to that action
- Admin sessions last 8 hours at most and end at once if access changes
- Users see their open sessions and can end any of them
Role and scope
Everyone sees only their own scope
Lecturers see only their own courses, students only their own record. On the management side, access is granted per person with a university-wide, faculty or department scope; the rectorate and department heads are not separate roles but permission templates built on these scopes.
- The “Top Management” template views every screen and changes nothing
- IT gets a read-only “System Observer” role
- Each module opens per person as none, read or write
No. The password is checked by the university’s identity service at every sign-in and is not kept in DAS. Password changes happen on the university’s account page.
