Kerio Workspace is a product that desperately needs an "elevator pitch". Everything else that Kerio sells is simple to explain: Connect is a mail server, Control is a firewall, and Operator programs phone systems. But what is Workspace?
At one of Kerio's own pages they say "Like Box and Google Docs, except it rocks". The trouble with that is that is that many, many people have no idea what Box or Google Docs are. Worse, while Workspace is somewhat similar to Box (https://Box.com), it really doesn't have much in common with Google Docs, which could further confuse people who are familiar with that but have never heard of Box.
What Kerio Workspace is most similar to is Microsoft Sharepoint. That bit of knowledge doesn't help you unless you are already familiar with Sharepoint, unfortunately.
Generically, Workspace is a browser based collaboration tool. It is a tool that helps groups of people work on projects. It is most useful when the project involves documents (spreadsheets, word processing files, images, whatever) that will be changed or added to, but it can be valuable even if the participants share nothing but text.
If you are composing an email where there is likely to be back and forth between the participants, you should be thinking about using a collaboration tool instead (see my Let's NOT have an email discussion about this!). If that email is inviting people to a meeting, a collaboration tool could augment and sometimes replace the meeting entirely.
This video shows how Kerio uses Workspace within their own organization; if you still don't see how this sort of tool is useful, watching this can help.
Google Docs is free and you can, with some clumsiness, use it as a collaborative tool.
Box for personal use is also free, though for business use it runs $180 per year per user (up to 500 users, "call for pricing" above that). Box does offer a free trial period so that you can kick the tires.
Microsoft Sharepoint is "free" with Server 2008, but of course Server 2008 isn't free and you also need to buy CAL's (client access licenses). Sharepoint pricing is confusing enough that you can find on-line pricing calculators to help you (Google for "sharepoint pricing calculator" after reading Microsoft's Sharepoint Licensing Details page and their System requirements page). This Determining the True Cost of Microsoft SharePoint might help also, but if you can tell me what Sharepoint really costs. you are a person of remarkable insight and patience.
Hosted Sharepoint is easier (at least with regard to pricing). A quick Google for "Sharepoint hosting" will turn up plenty of choices, most of whom will offer free trials.
Kerio's pricing is simple: $30 per user first year (that's per year, not per month), $10.00 per user subsequently; licensed in 5 user bumps only. It runs on Windows (you don't need a server version), Mac or Linux or under VMware. It's really that easy (see Kerio's web page for details). Hosted Workspace is also available, running from $10-$15 per user/per month (contact me for more information). You can download a free, 30 day demo from Kerio and trial hosting is also available.
Getting started with any of these tools is perhaps even harder than understanding why you would want to use them. Kerio Workspace is easy to use, but it is barely out of beta, so it lacks some features.
However, one of the really nice features of all Kerio products is customer feedback where you as a user can vote on desirable features.
If an idea is popular, it may get bumped up in priority by Kerio and will show as "Planned". This is a snapshot of those items in April of 2012 (some or all of these may already be implemented when you read this).
I wanted to mention that first so that you don't do too much "Fine, but what about.." as you read this overview.
The top level of Kerio Workspace is a "Space". You create Spaces, assigning them a name and adding sharing rights for other users. A Space is a container for "Pages", so think of it as an organizational unit. Pages that you create inside a space are also containers. Pages inherit the sharing permissions of the Space that encloses them by default, but you can set individual rights also.
Sharing rights are either "Reader", "Contributor" or "Admin".
Readers can view pages, Contributors can edit (including deletion; more on that later) and Admin access allows setting additional access rights in addition to having editing ability.
Example: A store is planning a major Spring sales promotion. The Space might be "Spring 2012 Sales Promotion". Within that space we might have a Page for "Newspaper Ads" and another Page for "Staffing". The people responsible for creatives would have at least "Contributor" access to the "Newspaper Ads" page and store managers would have that access to the "Staffing" page. All employees mighty have read access to "Staffing", but might not need access to "Newspaper Ads".
Note that if you want to share only some pages of a Space with another user, that user has to have at least Read access to the Space and then you'll have to remove access to the pages you do NOT want them to see. That's a bit clumsy; perhaps they'll provide an easier way later.
You don't have to be overly concerned about deletion. Everything can be "undeleted" by anyone with at least Contributor rights.
Being able to completely delete unwanted items is something that has been requested frequently and will be in a future version.
When you first create a Space, you have the choice of one, two or three column layout. Actually, all Pages have a three column layout; it's just a matter of which columns you choose to show and that can be edited at any time.
You adjust the width of columns just by dragging them wider; the height is dependent upon content (though you can also drag to increase the size of embedded content).
Every column of a page contains one or more components. A component can be simple text, an image, an embedded web page or video, a list of external links or a list of documents (File Library).
Sharing permissions cannot be assigned to individual components. I think it would be convenient if they could be, but you can accomplish this by breaking out separate pages with individual permissions.
Kerio Workspace can offer quick previews of some document types. At the present time, those include:
However, that doesn't mean that you are limited to those file types. For example, here I have added my 2011 Turbo Tax tax return to a File Library.
Kerio's free Desktop Client provides the integration to let you (or anyone with permissions) to launch a local computer application to edit the file. If I choose "Edit on Desktop", the Desktop Client will launch Turbo Tax and when I save and quit, will offer to upload the modified file to Workspace.
At the present time, the Desktop Client is available for Windows, Mac OS X and as a Firefox plug-in. I recommend installing the Desktop Client BEFORE trying to edit a file. Workspace will attempt to install this on the fly when first needed, but that can be very confusing.
This client is only a file helper. Your access to Workspace is through your browser, not a proprietary client.
Users can comment on individual components and can leave specific comments about any edits they are allowed to make. These comments appear in other users News Feed if they are subscribed to the Space.
By the way, when you add at least Read permissions, the Space shows up in the users "All Spaces" list automatically. They can drag it to Favorites if they wish.
One obvious feature available in competing products is anonymous guest access for at least viewing. That has been suggested, and has attracted a few votes, but hasn't reached "Planned" status as of this writing.
Of course there are other things, but there's no point in mentioning them as the next release may already incorporate them. As it stands now, Kerio Workspace is a useful collaboration tool at a quite reasonable price. You can download a free demo and I can also arrange for a free trial of hosted Workspace.
Got something to add? Send me email.
More Articles by Anthony Lawrence © 2013-06-18 Anthony Lawrence
[C has] the power of assembly language and the convenience of … assembly language. (Dennis Ritchie)