Hi Abbott:
After watching your your webcast ""How Microsoft IT Deployed Office Groove 2007" this morning I mentioned to Mike Gannotti how I really needed to dig into this application.
I'm really happy that you have decided to blog and I look forward to some great posts.
Abbott,
Well done, to what I look forward to being a great resource for Groove evangalists.
Looking forward to a 'public' Grooveypedia and lots of 'insider' info.
Regards
We seem to have found a bug involving permissions between Groove and SharePoint 2007. SharePoint 2007 now supports setting folder-level permissions within a Document Library. However, when you access the Document Library through Groove, you get full access to all of the folders in the Document Library whether you have permission on the folders in the SharePoint Document Library or not. Thus, by synchronizing a Document Library to a Groove Work Space, a user can use Groove to gain full access to folders for which they wouldn't have access in SharePoint. We tested this, and were able to successfully delete a whole folder on which the user was explicitly denied permissions through SharePoint. This seems to be a rather serious security flaw, as there isn't really any way to deny a user the ability to access a SharePoint Document Library through Groove.
Actually, this may be more of a SharePoint security issue, as I've also been able to access a folder for which I've been denied permissions by altering the URL; Groove just makes it much, much easier because the folders all show up and you don't have to already know the name of the folder.
We are a small software company, who, as well as using Groove extensively to collaborate internally, use Groove workspaces to share info and manage collaboration with new sites as we implement. Once an implementation is complete, we revoke the Groove license from the site and can re-allocate it using the Groove.net license management website.
We also create workspaces for our User Conference Planning Committee. Each member of the Committee is issued with a Groove license in January of each year, and licenses are revoked in September following the User Conference.
One of the great strengths of Groove Virtual Office 3.1 is the ability for us to share / revoke / re-issue licenses from our 'pool' in this way.
Here's the question: I have had a lot of trouble trying to figure out whether we will be able to continue with this practice of temporarily allocating our licenses to our sites or our Planning Committee members in Office Live Groove 2007. Microsoft has given me (by telephone) two completely conflicting answers. One answer is "Yes, as long as the person to whom you allocated a licence uninstalls the software, you can re-allocate it after 90 days". The other answer is "No you cannot assign your licenses to anyone outside your organization."
If we cannot continue to work in this way then we are in big trouble, but we don't want to break the law! Can anyone give me a definitive answer?