One of our regular readers, Mike in the Netherlands, sent me an email describing his trials and tribulations with Meeting Workspaces
. I'll quote the email here and look forward to your comments and war stories with Meeting Workspaces
In my effort to help users to step into “The new world of work” I encourage them to use team sites and organize their meetings with the use of a meeting workspaces.
Since each team member has member rights on the site they can add items to the calendar list. With that they also get the option to create a meeting workspace with a new (recurring) calendar item, and that’s where it gets wrong… since they are members they don’t have the right to create sites, however a meeting workspace is a site and therefore a user needs at least Manage Hierarchy rights.
The result: The team member is presented with a page: Error: Access Denied. Now he/she has two options, log in as another user or return to the site.
Users don’t get feedback from the system that the calendar item is actually created, although this is done without a meeting workspace.
Another remarkable thing is the breadcrumb path that is rendered at the top of the page of a meeting workspace.
In my view a meeting workspace is always created in the context of a (team)site. When looking at the URL this is indeed the case, however, looking at the breadcrumb you will see [Site Collection Name] -> [Meeting Workspace Name]. The whole context is gone and a user doesn’t have an option to navigate directly back to the team site from which the meeting workspace was opened.
Two things I can’t really sell at any client at all. Maybe I’m missing the concept behind it?
- Give the site member rights to create only meeting workspaces and no other type of sites
- Remove the option “Create meeting workspace” for site members, not preferable imho.