To prepare to switch to EliApps, you should view the Pre-migration checklist to ensure your account is ready for the transition. The EliApps Migration Utility is linked to from this checklist.

You will individually be invited to transition to EliApps via an official university message. The EliApps launch will be a rolling process and thus not all individuals will be notified at the same time. The email notification will include a link to the EliApps Migration Utility, which will require you to log in through the Central Authentication Service (CAS).

In most cases, no.

If you currently have an email alias in the form of first.last@yale.edu, your address will not change. If you do not currently have a first.last@yale.edu address (e.g. you are under non-disclosure), then your email address will change.

Note that if you have multiple aliases, they will be directed to your EliApps account. By default, you only be able to send from your primary alias. See sending mail from another address for instructions.

For instructions, see accessing your EliApps account.

Note: If you had previously set up your mail account on a computer or mobile device, you'll need to add your EliApps account as a new account.

Yes. In addition to the benefits of migrating to EliApps, it is important to understand that as of Fall 2012, central mail accounts will be deactivated. At that time, if you have not completed the migration, your email forward will also cease to exist.

If you are graduating on or before May 21, 2012 you may choose to opt-out of migration. To do so, please fill out the Class of 2012 EliApps Opt-Out Request form.

Students, faculty, and staff who are currently on non-YaleConnect email services (email.med or Pantheon) will be eligible to migrate to either EliApps or YaleConnect.

Yale undergraduates and graduate students in Arts & Sciences will migrate to EliApps.

Those with specific departmental and/or calendaring needs (i.e., delegation and sharing needs) and those with confidential or regulated data (i.e., ePHI) will migrate to YaleConnect.

ITS has already begun moving selected students and faculty from the Pantheon email servers to EliApps.

Increasing numbers of students and faculty will be invited to move to EliApps during the fall and spring semesters. The goal is to complete student migrations (excluding students in selected professional schools) by the end of the 2011-2012 academic year. Students and faculty who have regulated data will move to YaleConnect.

Faculty and staff will move over the course of the next two academic years. A deployment strategy is currently being created and the project team is working in tandem with lead administrators to help determine the most opportune time for departments to move from the Pantheon and email.med servers to either EliApps or YaleConnect. Some faculty and staff will be consolidated on the current YaleConnect service depending on business needs. Faculty and staff who use, access or transmit electronic protected health information (ePHI) or confidential data will move to YaleConnect. Conversations are underway with the professional schools to discuss specific deployment plans.

You will individually be invited to transition to EliApps via an official university message. The EliApps launch will be a rolling process and thus not all individuals will be notified at the same time. The email notification will include a link to the EliApps Migration Utility, which will require you to log in through the Central Authentication Service (CAS).

In addition to the frequently asked questions on this page, you may want to view the Pre-migration checklist to ensure that your account is ready to migrate.

The Student Technology Collaborative (STC) will assist students with transitioning to EliApps via documentation. In addition, training and documentation will be available for faculty and staff.

Mail: Similar to Google's Gmail service, except with a 25GB mail quota

Calendar: Personal and shared calendars

Sites: Personal website creation with videos, images, gadgets and documents integration

Docs: Web-based documents, spreadsheets, drawings and presentations that let users edit the same file at the same time so you always have the latest version. In addition, 1GB of storage for non-Docs files.

Chat: Text, voice, and video chat

Additional Google services may be offered after the initial EliApps launch.

EliApps provides a suite of communication and collaboration tools designed to enhance the ability of Yale students, faculty and staff to work together.

All undergraduate students must migrate to EliApps by Fall 2012, at which point central mail accounts will be deactivated.

There are two main advantages:

Storage - All EliApps accounts come with 25 GB of storage for your mail. In addition, there is an additional 1GB of storage for documents and more. Standard Gmail accounts allow less than 8 GB of storage.

Integration - By using your EliApps account, you can find and communicate with others at Yale. For example, you can easily invite other EliApps users to chat, share a calendar, attend an event, or share documents.

While this is possible using a standard GMail account, EliApps makes it easier and more reliable.

Your old email account will be deactivated 30 days after you have migrated from your Pantheon account to your EliApps account. You will no longer be able to log in to https://www.mail.yale.edu or access your old inbox once your old email account is deactivated. 14 days before your Pantheon email account is deactivated you will receive an automated email warning you that your Central Email/Pantheon account will be deleted. This is referencing your old email account and not your new EliApps account.

No. Once you have received an email from ITS telling you that you are eligible for EliApps, you can simply sign up with your NetID.

No, once you have migrated to EliApps you cannot go back to your Pantheon email account. You may access the Pantheon email for 30 days, but new mail will go to your EliApps account and after 30 days your Pantheon email account will be locked.

To prepare to switch to EliApps, you should view the Pre-migration checklist to ensure your account is ready for the transition. The EliApps Migration Utility is linked to from this checklist.

Messages in nested folders will be migrated. A single 'flat' label will be applied; the label name will match the full path of the folder (i.e. 'Folder/Subfolder' will be the label name). Labels are only created for folders that contain messages. In cases where a folder has a sub-folder, but no messages in the main folder, no label will be created for the main folder.

In most cases, no.

If you currently have an email alias in the form of first.last@yale.edu, your address will not change. If you do not currently have a first.last@yale.edu address (e.g. you are under non-disclosure), then your email address will change.

Note that if you have multiple aliases, they will be directed to your EliApps account. By default, you only be able to send from your primary alias. See sending mail from another address for instructions.

Yes, you may continue to use your current email program, however, you will need to set up a new account in your current program. Instructions on configuring your client are available at the email configuration page. In addition, you will have the ability to access your email and the rest of the EliApps offerings through the Google web interface.

In general, no. Once the mail migrations are complete, most students, faculty, and staff will have either a Yale Connect or an EliApps account.

No. There will be no significant changes to the process of requesting and provisioning email accounts.

No, your Yale credentials are independent of any other Google accounts you may have.

There will be no impact to the AYA email forwarding services. In the future, other options may be available.

Your current forwarding will be removed and messages will go to your new EliApps account. If you would like to resume forwarding you will need to set your forwarding again, see Google's instructions on forwarding mail to another email account automatically.

See Google's instructions on forwarding mail to another email account automatically.

Note:If you enable forwarding while your mail is being migrated using the migration utility, any mail migrated to EliApps will also be forwarded.

For more info on EliLists, see the EliLists FAQ.

Yes, students, faculty and staff using EliApps will see an immediate improvement in their ability to schedule meetings and share calendars. While there is no direct integration between EliApps and YaleConnect calendars at this time, individuals can send and receive meeting invitations between the two systems. You will not be able to view "free/busy" information between systems.

Yale ITS is investigating how to further directly integrate the two systems at the current time.

By default, your "free/busy" calendar information is shared with everyone using EliApps. If you would like to require that anyone who wants to view your calendar request permission directly from you, you may disable sharing of your "free/busy" information. Please note that if you do so, people will not be able to easily schedule meetings with you as they will not know your availability. Instructions on hiding your "free/busy" information are available.

Yes. Instructions on sharing your calendar with another EliApps user are available.

Yes. Instructions on requesting permission to view or manage another user's EliApps Calendar are available.

There are a few different ways that you can handle your personal Gmail account and your EliApps account. There are benefits and drawbacks to each which you should understand and make your decision accordingly.

You may also be interested in the advantages of using an EliApps account over standard Gmail.

Forwarding: You can set your EliApps account to automatically forward your messages to Gmail. Doing so will consolidate all of your messages into a single account. From your Gmail calendar you will not be able to see the calendar events of other EliApps users for scheduling purposes, however, you would be able to invite them to your events. You would be able to cross-collaborate with EliApps users on shared Docs files.

Instructions for forwarding your EliApps mail to Gmail

Multiple Sign-in: If you'd like to be able to sign in to multiple accounts in the same browser, you can enable the multiple sign-in setting. This will allow you to sign in to more than one account using the same browser session. You can sign in to ten accounts at a time. Not all Google products support multiple sign-in, so the account you are using may change, so you need to be aware of the account that you are signed into at any given time. That account is generally listed in the upper right corner of your browser window.

Instructions for enabling multiple sign-in
Instructions for using multiple sign-in

We have every reason to believe that Google will take security seriously and our data will be just as secure as it is now.

Yes, Google will safeguard individual privacy of our email and data. In addition to the standard privacy practices that Google offers to all its users, Yale also has a signed contract with Google that guarantees privacy and confidentiality in ways that are analogous to the way Yale currently provides email services.

Google asserts that Yale will retain possession of EliApps data. “Data mining” and vending ads are NOT part of the service package for EliApps accounts.

Employees who access, store or transmit electronic protected health information (ePHI) will not use Google; they will have YaleConnect (Exchange) email accounts.

Servers are housed in Google's data centers - Google does not disclose the exact locations of their servers for security reasons. The content of each email or document is spread around to several different physical data center locations so that in the unlikely event that one of Google's data centers is compromised, your data will still be protected. This is actually much more rigorous than the security of our existing service.

As long as appropriate care is taken in sharing information, EliApps may be used to store or transmit most information, including student grades and other information protected by the Family Educational Rights and Privacy Act (FERPA). When using EliApps to store or transmit FERPA-protected education records, you must use all the same precautions, including double-checking the address, that you used when storing or transmitting this information with your previous Yale email application.

EliApps may not be used to store or transmit files that contain Social Security numbers, Protected Health Information, or information governed by federal export-control laws.

Policies and regulations change, so be cautious. If you are concerned or have questions, please consult the Office of the General Counsel.

Yale's adoption of Google Apps for Education is a positive step forward in reducing ITS operating costs while offering an expanded suite of collaborative tools beneficial to the Yale community.

Yes, Google is providing the service for free, although contractually Google can raise the rates or even stop providing the service with appropriate advance notice to Yale so that Yale can find alternative solutions. Bear in mind that Google doesn’t have to provide the service “free” for it to be more cost effective than Yale providing the service. There are other vendors in the marketplace like Microsoft and Yahoo who will help keep the market prices balanced, but we’re not locked into a “special” deal with Google as our only choice.

Yes, the Google Apps screens will be customized with the Yale brand. In addition, the service will be referred to as EliApps.

No, EliApps will not display any advertising or “recommended links.”

Both by terms of service and by reputation we do not anticipate any change from the current level of service.

Yes, our capabilities will remain unchanged, although in a few nuanced and unlikely circumstances we will have less capability. We retain the ability to investigate what information is currently in a student’s Yale email account but we may not have as much secondary information since less of the network traffic will occur on Yale’s network.

Within the Ivy League, Brown, Cornell, and many of the professional schools at Harvard have moved to Google. Indiana, USC, Temple, Notre Dame, Arizona State University and the University of Wisconsin are also using Google Apps.

No, there will be no significant changes to the IT Appropriate Use Policy, users will be bound to the same standards.

Yale will maintain current standards and policies.