I had a user who left our company but while she was here she created a calendar and shared it with most of the people she worked with. How can I transfer ownership of this calendar to someone else so they can share it will new staff.
Printable View
I had a user who left our company but while she was here she created a calendar and shared it with most of the people she worked with. How can I transfer ownership of this calendar to someone else so they can share it will new staff.
I don't think you can do this now. Can you file an enhancement request in bugzilla for this (moving entire folders between users)? We're going to support moving individual items between users for the 5.0 release (bug 7129), but moving entire folder hierarchies is not part of that bug.
For now, can you grant someone admin rights on the calendar using zmprov and then just share the existing calendar with new staff?
Great. This sounds exactly what I've been looking for.
However, could you give us an example of what a command that grants "admin rights" on a calendar would look like?Quote:
Originally Posted by dkarp
For instance, let's assume we want to grant admin priviliges to "jdoe" on calendar "holidays"?
I've been perusing the docs and the wiki, and it's not that clear how to accomplish it, and considering the potential for trouble doing this by trial and error, I'd feel better seeing a working example first.
Thanks
I've been looking into a similar problem because we're setting up a new installation and I want to share our meeting room resource calendars with everybody.
The answer looks like using zmmailbox rather than zmprov.
Through the cli, the following appears to work:
zmmailbox
mbox> aa admin MY_ADMIN_PASSWORD
mbox> sm resource
mailbox: resource@example.com, size: 0 B, messages: 0, unread: 0
mbox resource@example.com> mfg /Calendar all r
It's a little maddening because the help doesn't list what the acceptable values are for permissions, but they appear to be "r for read", "w for write" and "a (for admin?)", or any combination thereof.
After setting the permission to "r", users were able to subscribe to the calendar.
In your case, you probably want "raw".
For command line use, the following also works for me.
% zmmailbox -z -m resource mfg /Calendar all r
Hope this helps!
Once you've shared your resource, you can automatically subscribe people to it!
zmmailbox -z -m USER cm -V appointment -c purple /Central\ Boardroom resource /Calendar
Very handy if, for example, you're writing a script to set things up for new users.
It's much easier for a new user to ignore or delete shared resources they don't want then to find out what resources they should have and figure out how to add them.
Now I just need an ics feed for Company Holidays and we'll be good to go.
The way we avoid this in the first instance is to create a non-human account to use for broadly shared calendars and contacts folders.
Something like "ShareMonkey@yourdomain.com" for example.
Then, you can log in as the sharemonkey account and share out the calendars and contacts lists you need to.
Sharemonkey's email can get forwarded to a real human if need be, but regardless, having a non-human account for these kinds of things means never having to worry about what happens when a key employee with a lot of shared items leaves.
Hope that helps,
Mark
Is this still the case in Zimbra 8.0.2? I am in the exact same situation as the original poster. The assistant to our superintendent (I work for a school district) has retired. She created two calendars that are shared with our administrative team. Is there still no way to change ownership of said calendars?
This is still working as originally intended, which is why the non-human mailbox technique avoids the problem with retiring or otherwise departing employees.Quote:
Originally Posted by thunder04
If I may, I'd suggest the following:
- Export the Calendars from the Superintendent's Assistant's mailbox.
- Create a new non-human mailbox as described above in this thread.
- Import the Calendars into this new non-human mailbox.
- Share out the Calendars from the non-human mailbox to designated staff, ensuring at least one staff member has at least Manager privileges.
- Once staff have accepted the shares and confirmed all is well, from the Superintendent's Assistant's mailbox revoke all the shares for those two Calendars.
- Life cycle the Superintendent's Assistant's mailbox as per your policies.
Hope that helps,
Mark
Thanks for the quick reply!
I figured that was the case, but I wanted to check first. I'll move the calendars to a non-human account and re-share.