Redirect, auto reply etc.
The current approach has been ad-hoc. A standardised one is needed.
In particular suspending an account also kills the e-mail address meaning no customised auto-reply can be used.
| Sebastian_Berlin-WMSE | |
| Nov 23 2020, 11:55 AM |
Redirect, auto reply etc.
The current approach has been ad-hoc. A standardised one is needed.
In particular suspending an account also kills the e-mail address meaning no customised auto-reply can be used.
Suggested is:
After X months.
Still undecided:
The above considers a case where the person does not wish to keep their e-mail in a volunteer capacity.
@Lokal_Profil, we should make a decision on this. Alternatively we'll have to sit down and figure it out when it happens next, which probably won't be the best timing.
What happens when we "Set the account to suspended"?
I do think we should have a routine to check in to the email at least the following 2 years to catch the type of semi-recurring requests for joint activities that we get now and then.
From https://support.google.com/a/answer/33312:
When you suspend an account, the user's:
- Email, documents, calendars, and other data aren't deleted.
- Collaborators who have been granted access to shared documents will retain their ability to view, edit, and collaborate on those documents.
- New email and calendar invitations are blocked.
I also believe suspending means that you can't log into the account or use it in any other way.
It looks like we can use a group for auto replies: https://bulksignature.com/blog/how-to-set-up-auto-replies-for-departing-employees-on-google-workspace. That way we can have the same message for all previous employees and if we want to update it we only need to change it in one place.
The above seems to only allow for a generic message. If they want to have a custom one, for instance with their new email address, they need to set it themselves before leaving.