Campus login and identity
MyESADE centers on a branded login flow for ESADE users, with email and password fields presented before deeper campus services. This makes the app most relevant to people who already belong to the institution.
Use only your own school credentials and keep the device locked. Campus accounts can connect to schedules, messages, academic data, or administrative services depending on the account.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
Notifications and student workflow
A dedicated campus app can help users receive alerts, check school-related information, and keep institutional services separate from a browser. The branded interface suggests a focused ESADE workflow rather than a general public utility.
Review notification settings so school alerts stay useful without exposing private information on the lock screen. Shared devices are a poor fit for academic account access.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
Location, Bluetooth, and biometric access
The package declares Bluetooth, precise and approximate location, notifications, biometric or fingerprint access, boot receiver, network access, wake-lock, and push messaging. These permissions can support campus proximity features, secure sign-in, and alert delivery.
Grant location or Bluetooth only when a campus feature clearly needs them. Biometric sign-in should be enabled only on a personal, trusted device.
This gives the section a clearer user value by connecting the main feature to a concrete mobile use case, session goal, or replay reason.
