Delegate Access for Emails Policy


Contents

Permission may be granted for one email user to act on behalf of another email user, also known as delegate access. There are two types of delegate access:

Send on Behalf

This permission allows a user to send emails that are marked as, "on behalf of" another user. Messages sent with Send on Behalf permissions include both the delegate's and the account owner's name, so the authorship of the email is transparent.

Send As

This permission allows emails to be sent as if directly coming from another user or office or initiative (e.g. UChicago Citizen and Campus & Student Life) . Messages sent with Send As permissions include only the account owner's name. When an email is sent using the Send As feature, the authorship of the email is obscured. In these cases, the email appears to come from the account owner, even though this is not necessarily the case.

The University of Chicago considers emails accessed or created using delegate access to be confidential information. University Policy 601 on the Treatment of Confidential Information states that employees are required to safeguard confidential information and only use or disclose it as expressly authorized or specifically required in the course of performing their specific job duties.

Misuse of confidential information can include but is not limited to:

Specifically, in regards to Delegate Access for Emails, misuse includes:

Employee misuse of confidential information and/or delegate access to emails is a serious breach of job responsibilities and will result in discipline such as:

In addition to following the Policy on Delegate Access, I understand that all staff are required to follow the University of Chicago IT Policies at all times.