Certain applications, such as Asana, utilize the domain address of the user's email as a method of authenticating new users into their system when utilizing their Organization features. In our case, ses.edu is the root domain through which all of our emails are routed. Asana does not allow us to utilize their Organization feature, as it specifically requires that users under a .edu domain NOT have their emails under the root domain. This is done to prevent students from being able to register an account and have access to private resources, as it uses the domain of the email addresses to authenticate a user into the organization. Apart from this specific limitation in our workflow, having a unique subdomain for student accounts helps further the distinction between the student accounts and the staff or faculty.
Simply put, being able to have our students emailed @students.ses.edu, rather than our root domain would be a convenient feature. Furthermore, @staff.ses.edu and @faculty.ses.edu would also be nice distinctions to have. Those who are both Staff and Faculty simultaneously may simply have an email alias applied, with the @staff.ses.edu being the primary alias. I still don't know if that is the way I want to do it, but at the very least, being able to distinguish staff and faculty emails from students' at a domain level would be useful for us.