Main Nav

Hi Randy….. a few years ago, we took a position paper to our IT Governance body (all the VP’s across the Institute) and proposed NOT offering email at all to students.  It was (in our opinion) becoming a dis-service to do it as most by far already arrived here with an email address and this just meant one more to manage, keep track of, forward to someplace they actually looked……. 

 

We had also moved to a “secure message center” model where we provided for everyone – through a web interface, a secure message center where we would put official communications, and we would just send their “preferred email address” (which we collect in Banner) a note telling them there was a message waiting for them (similar to how financial institutions never put payload in the actual email message – but instead authenticate you to a message center).  That way we could also see who had logged in and opened the messages.

 

Cheers
Dave

 

 

 

 

David Cresswell, MBA
  Assoc. Director, Strategic Practices

   
IT Services
British Columbia Institute of Technology
3700 Willingdon Avenue, Burnaby, BC, V5G 3H2

Tel: 604.432.8729 · Mobile: 604.341.7420 · Fax: 604.439.6785
Email: Dave_Cresswell@bcit.ca · Web: bcit.ca/its

If you need technical support, please contact us online or by phone at: techhelp@bcit.cahttp://www.bcit.ca/techhelp •  604 412-7444 • 1-800-351-5533 (toll-free)




P
Please consider the environment before printing this e-mail.
_______________________________________________________________

 

Comments

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.
--
Wake Forest University


Randy,

-We use Gmail for our students email – the suffix is student.fitchburgstate.edu  
-Six months after they graduate, they move over to falcon.fitchburgstate.edu and they can keep that for life (different domain on Gmail).  This separates our current students from our alumni and gives them time to respond to job offers after they have graduated and is handled automatically by our identity management software (Tools4Ever). 
-We do the same for faculty/staff that retire (a Gmail "falcon" account), though this is a manual process as we usually work with them to export and import their contacts.  If a student is no longer active, but has not graduated, their email stays active for 18 months and then is disabled.  Employees that leave are disabled (there may be a time when out-of-office directs inbound messages to their replacement) on termination.
-Employees that are also students: they get a gmail account but are instructed on how to forward that email to their work (Outlook) account.

I hope that helps!

__________________________
Steve Swartz
Chief Information Officer
Fitchburg State University
978-665-4444



Hi, Randy,
We are a Google Apps environment.
Only specific faculty members meeting a set of requirements on retirement, under the contract, are entitled to email for life. 
Other faculty departures may maintain their account for one year, as they work through the final processes of grading and submitting materials related to courses and such.
Students maintain an account for one year after the end date of their last registered term, whether or not they graduate.
Everyone else has an account that is terminated 24-48 hours after termination for any reason.

Because we are a single-sign-on environment with many services attached to the LDAP entry, with email being just one of those services, this is the solution that works best for all services, some of which have the access time period limited by contract or license. 

Theresa


Anne,

We also discussed this. In these times, sourcing decisions are critical ones and also part of a larger strategic direction. We felt the risk of a switch to a fee-based service was less than the gain (savings in staff time and avoided infrastructure costs, and provision of a rich collaboration environment). There is an intangible benefit in that it allows us to experience and learn more about placing such an important set of collaboration tools in the cloud, where I believe many of our services are headed. 

We reinvested some of our savings into Google Vault for e-discovery, thereby reducing institutional risk. 

Do I think the service will remain free for 5-10 years or more? I'm not betting on that, just as I'm not betting on our ERP vendor maintenance costs being sustainable (well, I can push the "easy" button on that one, I suppose, as they already aren't sustainable).  

One thing we all know in IT is that no sourcing decision is "once and done." Our requirements change, costs change, vendors come and go, contracts sunset and new ones become untenable. I'm very comfortable with our Google Apps for Education decision. As with all major systems, we will continue to keep our eyes on the institutional and IT horizon looking for the need to reassess.  

Regards,
Debi Allison
Vice President for Information Technology and CIO
Miami University
Sent from my iPhone



From: Anne Toal <HARWELL@UTPA.EDU>
Reply-To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Date: Wednesday, June 5, 2013 2:52 PM
To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Subject: Re: [CIO] email for life for faculty/staff

The names of free cloud email services frequently come up when discussing the topic of free email for life. Does everyone assume that these services will be free for life to the institution? If you’re providing free email for life to a population of people who no longer study or work at the institution, and your cost of providing those email accounts suddenly goes up (say through changed terms in an outsourcing contract), what do you believe your institution’s response ought to be?

 

Thank you,

Anne Toal

UTPA Technology Assessment Officer

 

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Matthews, Rick
Sent: Wednesday, June 05, 2013 1:22 PM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.

--

Wake Forest University

 

Anne,

We also discussed this. In these times, sourcing decisions are critical ones and also part of a larger strategic direction. We felt the risk of a switch to a fee-based service was less than the gain (savings in staff time and avoided infrastructure costs, and provision of a rich collaboration environment). There is an intangible benefit in that it allows us to experience and learn more about placing such an important set of collaboration tools in the cloud, where I believe many of our services are headed. 

We reinvested some of our savings into Google Vault for e-discovery, thereby reducing institutional risk. 

Do I think the service will remain free for 5-10 years or more? I'm not betting on that, just as I'm not betting on our ERP vendor maintenance costs being sustainable (well, I can push the "easy" button on that one, I suppose, as they already aren't sustainable).  

One thing we all know in IT is that no sourcing decision is "once and done." Our requirements change, costs change, vendors come and go, contracts sunset and new ones become untenable. I'm very comfortable with our Google Apps for Education decision. As with all major systems, we will continue to keep our eyes on the institutional and IT horizon looking for the need to reassess.  

Regards,
Debi Allison
Vice President for Information Technology and CIO
Miami University
Sent from my iPhone



From: Anne Toal <HARWELL@UTPA.EDU>
Reply-To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Date: Wednesday, June 5, 2013 2:52 PM
To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Subject: Re: [CIO] email for life for faculty/staff

The names of free cloud email services frequently come up when discussing the topic of free email for life. Does everyone assume that these services will be free for life to the institution? If you’re providing free email for life to a population of people who no longer study or work at the institution, and your cost of providing those email accounts suddenly goes up (say through changed terms in an outsourcing contract), what do you believe your institution’s response ought to be?

 

Thank you,

Anne Toal

UTPA Technology Assessment Officer

 

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Matthews, Rick
Sent: Wednesday, June 05, 2013 1:22 PM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.

--

Wake Forest University

 

I have looked at the archives for this list as well as the CDS and have not found an exact answer...although I think I know the answer..
Still I would like some current feedback for those of you that have the time to respond.
At Idaho State University we offer faculty, staff, and students...email for life...through Google...no separation among the groups by naming convention or anything.
In some cases, when an employee is terminated, we take email privileges away permanently...but that is rare.
I have been asked by our president to assess best practices...what are others doing?
Do you offer email for life for faculty and staff?
If you do not...do you offer email for life to students, and if so, how do you handle students who may also be employees? (seems the consensus here might be to provide different email accounts?).
Thanks as always, in advance for any help.
Randy


--
Randy Gaines
Chief Information Officer
Idaho State University
gainrand@isu.edu
208-282-2499
http://www.isu.edu
Leading in opportunity and innovation
********** Participation and subscription information for this EDUCAUSE Constituent Group discussion list can be found at http://www.educause.edu/groups/.

Randy,

We provide Google Apps for Education to all students, faculty and staff. Students and emeriti/retirees get accounts for life (as was the case with our previous Exchange implementation). Faculty and staff who leave employment without retiring do not retain their accounts. 

Thanks,
Debi
Sent from my iPhone

Hi Randy….. a few years ago, we took a position paper to our IT Governance body (all the VP’s across the Institute) and proposed NOT offering email at all to students.  It was (in our opinion) becoming a dis-service to do it as most by far already arrived here with an email address and this just meant one more to manage, keep track of, forward to someplace they actually looked……. 

 

We had also moved to a “secure message center” model where we provided for everyone – through a web interface, a secure message center where we would put official communications, and we would just send their “preferred email address” (which we collect in Banner) a note telling them there was a message waiting for them (similar to how financial institutions never put payload in the actual email message – but instead authenticate you to a message center).  That way we could also see who had logged in and opened the messages.

 

Cheers
Dave

 

 

 

 

David Cresswell, MBA
  Assoc. Director, Strategic Practices

   
IT Services
British Columbia Institute of Technology
3700 Willingdon Avenue, Burnaby, BC, V5G 3H2

Tel: 604.432.8729 · Mobile: 604.341.7420 · Fax: 604.439.6785
Email: Dave_Cresswell@bcit.ca · Web: bcit.ca/its

If you need technical support, please contact us online or by phone at: techhelp@bcit.cahttp://www.bcit.ca/techhelp •  604 412-7444 • 1-800-351-5533 (toll-free)




P
Please consider the environment before printing this e-mail.
_______________________________________________________________

 

So Dave, did I read your post correctly?  BCIT no longer provides institutional email to students?  If so, how has that been working out?  Any others out there who no longer provide an institutional email account to students?

Steve


Steve Smith, Assoc VP/Deputy CIO
University of Hawaii
 


My take on these practices has changed now that I work at an adult-focused institution with a very large fraction of adjunct faculty :-)  I'd love to hear more from others who are in similar boats.

A four-part primer:
  1. It is common for us to have regular employees (and adjuncts) who are or become students.
  2. It is common for us to have staff who also teach as adjunct faculty (some rarely, some frequently; some on-load, some off; the teaching relationship often continues after regular employment ends)
  3. It is common for us to have adjunct faculty who don't teach for years, but then come back and teach again. Often with little advance notice. It's quite common for new employees to be moving from adjunct status, and continue teaching on or off load.
  4. It is common for us to have students take many terms off and then return to their studies. Sometimes this is according to plan, sometimes it's a last-minute decision. It is common for us not to know their plans in advance. 

Some things that don't work well in this situation:
 -naming conventions based on role
 -firm rules about taking away email accounts from adjuncts who aren't teaching
 -thinking that admissions or hiring is the start of the relationship, or that stop-out, graduation, or employee separation is the end
 
The short answer is that we plan to grant role and privs-based, rather than account-based, access. Accounts will stay there a long time. As usual in such a system, privs are the union of the highest granted by all the individual's current roles.  We're trying to structure our Google subdomains and OUs to manage access and risk in intelligent ways given all this fuzziness.  It's not easy.

Back to the precise question: we are working with HR to try to document their practices and policies, so IT can follow them. But in many ways IT has more skin in this game than HR. Whether or not HR thinks you are on the books as an adjunct is a one-time annoyance when you sign up to teach again (application, background check) but IT is threatening to take away your Google account! It makes for an interesting discussion.

Dave's point (just don't give email to students) is good, but since we are on Google the account is not just email but a hub for collaboration. We believe that there is significant value in providing students and faculty with this shared collaborative environment. 

Ethan



——

Ethan Benatan, Ph.D.
Vice President,
Chief Information Officer, and Chief 
Strategy Officer
503.699.6325 (o)  / 
503.528.6713 (m)  

MARYLHURST UNIVERSITY
You. Unlimited.


Hi Steve!

 

We have had our proposal approved by our Governance body.  However, while we are still on Luminis 4.x for our portal we can’t extricate the integrated email that comes with the Oracle/Sun environment. So students still get email addressed generated but we ask them which email address they would prefer to have us use to notify them of a waiting communication in the Secure Message Centre.

 

Once we get past Luminis 4.x (soon I hope) we will be able to then peel back the integration and not have to even generate them. 

 

It is a resource consumption (Sys admins time, servers, backup, etc ) that essentially provide no (or little) value so we would rather direct our resources at higher value activities.  

 

D

 

 

David Cresswell, MBA
  Assoc. Director, Strategic Practices

   
IT Services
British Columbia Institute of Technology
3700 Willingdon Avenue, Burnaby, BC, V5G 3H2

Tel: 604.432.8729 · Mobile: 604.341.7420 · Fax: 604.439.6785
Email: Dave_Cresswell@bcit.ca · Web: bcit.ca/its

If you need technical support, please contact us online or by phone at: techhelp@bcit.cahttp://www.bcit.ca/techhelp •  604 412-7444 • 1-800-351-5533 (toll-free)




P
Please consider the environment before printing this e-mail.
_______________________________________________________________

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Steve Smith
Sent: Wednesday, June 05, 2013 11:12 AM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

So Dave, did I read your post correctly?  BCIT no longer provides institutional email to students?  If so, how has that been working out?  Any others out there who no longer provide an institutional email account to students?

 

Steve

 


Steve Smith, Assoc VP/Deputy CIO

University of Hawaii

 

 

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.
--
Wake Forest University


Randy,

-We use Gmail for our students email – the suffix is student.fitchburgstate.edu  
-Six months after they graduate, they move over to falcon.fitchburgstate.edu and they can keep that for life (different domain on Gmail).  This separates our current students from our alumni and gives them time to respond to job offers after they have graduated and is handled automatically by our identity management software (Tools4Ever). 
-We do the same for faculty/staff that retire (a Gmail "falcon" account), though this is a manual process as we usually work with them to export and import their contacts.  If a student is no longer active, but has not graduated, their email stays active for 18 months and then is disabled.  Employees that leave are disabled (there may be a time when out-of-office directs inbound messages to their replacement) on termination.
-Employees that are also students: they get a gmail account but are instructed on how to forward that email to their work (Outlook) account.

I hope that helps!

__________________________
Steve Swartz
Chief Information Officer
Fitchburg State University
978-665-4444



Hi, Randy,
We are a Google Apps environment.
Only specific faculty members meeting a set of requirements on retirement, under the contract, are entitled to email for life. 
Other faculty departures may maintain their account for one year, as they work through the final processes of grading and submitting materials related to courses and such.
Students maintain an account for one year after the end date of their last registered term, whether or not they graduate.
Everyone else has an account that is terminated 24-48 hours after termination for any reason.

Because we are a single-sign-on environment with many services attached to the LDAP entry, with email being just one of those services, this is the solution that works best for all services, some of which have the access time period limited by contract or license. 

Theresa


We provide a lifetime account for students who complete any course.  We also provide a lifetime account for retirees but for employees who terminate for other reasons.  Our email systems are separate with faculty, staff and retirees using on-premise MS-Exchange and students using Google.

 

Even if we used the same email system, keeping track of who gets to keep the account would not be difficult because we keep track of separate affiliations for faculty, staff, retirees, current students and anyone who has attended the university.  If you have any valid affiliation needed for the account you would get to keep it.

 

Chris Michels

Director Computing and Communications Systems

Information Technology Services

Northern Arizona University

928-523-6495

 

Message from harwell@utpa.edu

The names of free cloud email services frequently come up when discussing the topic of free email for life. Does everyone assume that these services will be free for life to the institution? If you’re providing free email for life to a population of people who no longer study or work at the institution, and your cost of providing those email accounts suddenly goes up (say through changed terms in an outsourcing contract), what do you believe your institution’s response ought to be?

 

Thank you,

Anne Toal

UTPA Technology Assessment Officer

 

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Matthews, Rick
Sent: Wednesday, June 05, 2013 1:22 PM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.

--

Wake Forest University

 

Anne,

We discussed this internally when we started doing this.  The reality: I doubt email will be around for the life of the institution.  We'll reassess the program if that happens, which would really be like any other — if our faculty email prices suddenly increased 1000% we'd look at that too.  We send our billing through email which forces the usage, but our student population is rapidly declining to a state where they are unable to create a sentence longer than a text message allows.

__________________________
Steve Swartz
Chief Information Officer
Fitchburg State University
978-665-4444

From: Anne Toal <HARWELL@UTPA.EDU>
Reply-To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Date: Wednesday, June 5, 2013 2:52 PM
To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Subject: Re: [CIO] email for life for faculty/staff

The names of free cloud email services frequently come up when discussing the topic of free email for life. Does everyone assume that these services will be free for life to the institution? If you’re providing free email for life to a population of people who no longer study or work at the institution, and your cost of providing those email accounts suddenly goes up (say through changed terms in an outsourcing contract), what do you believe your institution’s response ought to be?

 

Thank you,

Anne Toal

UTPA Technology Assessment Officer

 

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Matthews, Rick
Sent: Wednesday, June 05, 2013 1:22 PM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.

--

Wake Forest University

 

To Anne’s point, we are in the process of moving from Live email for current and former students to Office 365 and we found that the upgrade cost and complexity for this generally “free” solution about doubled if we upgraded both current and past student accounts. It is very easy to imagine various add-ons and services getting re-priced in the future where parts or all of it will no longer be free. I haven’t fully thought through potential legal discovery and hold issues but that too may add to the complexity. Our helpdesk also gets calls from current and past students. To better utilize our resources we have made the decision to start discontinuing accounts 2 years after students graduate. There are certainly other ways to remain connected to the former students.

 

Ilya Yakovlev

CIO

University of Wisconsin-Parkside

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Anne Toal
Sent: Wednesday, June 5, 2013 1:53 PM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

The names of free cloud email services frequently come up when discussing the topic of free email for life. Does everyone assume that these services will be free for life to the institution? If you’re providing free email for life to a population of people who no longer study or work at the institution, and your cost of providing those email accounts suddenly goes up (say through changed terms in an outsourcing contract), what do you believe your institution’s response ought to be?

 

Thank you,

Anne Toal

UTPA Technology Assessment Officer

 

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Matthews, Rick
Sent: Wednesday, June 05, 2013 1:22 PM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.

--

Wake Forest University

 

Randy,

 

·         All retired faculty are allowed to keep their e-mail account if they request it through HR.

·         We recently implemented a new policy which allows retired staff to keep their accounts if they meet the following criteria: Must have a minimum of 10 years of service and their time in service and age at time of retirement must add up to at least 70. And they must request through HR that the account remain active.

·         Graduates are allowed to keep their e-mail for as long as they continue to use it or if they have their messages forwarded to another account. We delete the account if it’s been active for longer than 18 months and isn’t forwarded.

 

Good luck!

 

Mickey

*******************************************************************************

Michael R. Belote

Chief Technology Officer

Mercer University

O: 478-301-2850

M: 478-719-2955

http://IT.Mercer.edu

 

Anne,

We also discussed this. In these times, sourcing decisions are critical ones and also part of a larger strategic direction. We felt the risk of a switch to a fee-based service was less than the gain (savings in staff time and avoided infrastructure costs, and provision of a rich collaboration environment). There is an intangible benefit in that it allows us to experience and learn more about placing such an important set of collaboration tools in the cloud, where I believe many of our services are headed. 

We reinvested some of our savings into Google Vault for e-discovery, thereby reducing institutional risk. 

Do I think the service will remain free for 5-10 years or more? I'm not betting on that, just as I'm not betting on our ERP vendor maintenance costs being sustainable (well, I can push the "easy" button on that one, I suppose, as they already aren't sustainable).  

One thing we all know in IT is that no sourcing decision is "once and done." Our requirements change, costs change, vendors come and go, contracts sunset and new ones become untenable. I'm very comfortable with our Google Apps for Education decision. As with all major systems, we will continue to keep our eyes on the institutional and IT horizon looking for the need to reassess.  

Regards,
Debi Allison
Vice President for Information Technology and CIO
Miami University
Sent from my iPhone



From: Anne Toal <HARWELL@UTPA.EDU>
Reply-To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Date: Wednesday, June 5, 2013 2:52 PM
To: EDUCAUSE Listserv <CIO@LISTSERV.EDUCAUSE.EDU>
Subject: Re: [CIO] email for life for faculty/staff

The names of free cloud email services frequently come up when discussing the topic of free email for life. Does everyone assume that these services will be free for life to the institution? If you’re providing free email for life to a population of people who no longer study or work at the institution, and your cost of providing those email accounts suddenly goes up (say through changed terms in an outsourcing contract), what do you believe your institution’s response ought to be?

 

Thank you,

Anne Toal

UTPA Technology Assessment Officer

 

 

From: The EDUCAUSE CIO Constituent Group Listserv [mailto:CIO@LISTSERV.EDUCAUSE.EDU] On Behalf Of Matthews, Rick
Sent: Wednesday, June 05, 2013 1:22 PM
To: CIO@LISTSERV.EDUCAUSE.EDU
Subject: Re: [CIO] email for life for faculty/staff

 

Context: we are a Google Apps for Education campus

  • We provide email (and calender, docs, sites, etc.) to all faculty, staff, and students.
  • Retired faculty have email for life. Staff (mostly) do not.
  • Students have had email forwarding for life, but are lobbying very heavily for email and Google Apps for life. The Google Apps piece is a big deal for them, as much of their intellectual output from their time here is in Google Docs, Sites, etc.  We want to do this as soon as we can determine an effective way of migrating them to an alumni domain.

--

Wake Forest University

 

Close
Close


Connect: San Antonio
April 22–24
Register Now

Events for all Levels and Interests

Whether you're looking for a conference to attend face-to-face to connect with peers, or for an online event for team professional development, see what's upcoming.

Close

Digital Badges
Member recognition effort
Earn yours >

Career Center


Leadership and Management Programs

EDUCAUSE Institute
Project Management

 

 

Jump Start Your Career Growth

Explore EDUCAUSE professional development opportunities that match your career aspirations and desired level of time investment through our interactive online guide.

 

Close
EDUCAUSE organizes its efforts around three IT Focus Areas

 

 

Join These Programs If Your Focus Is

Close

Get on the Higher Ed IT Map

Employees of EDUCAUSE member institutions and organizations are invited to create individual profiles.
 

 

Close

2015 Strategic Priorities

  • Building the Profession
  • IT as a Game Changer
  • Foundations


Learn More >

Uncommon Thinking for the Common Good™

EDUCAUSE is the foremost community of higher education IT leaders and professionals.