Workspace Code Released in Plone Intranet Development Sprint (July 2014)

Matt Sital-Singh

Netsight finished this development sprint by releasing ‘ploneintranet.workspace 1.0’, a key building block for flexible team / community workspaces on intranets.

Plone Intranet sprint

After another successful development sprint, we are pleased to announce the release of ploneintranet.workspace 1.0!

We covered some of the background to this development in our previous blog post, but this sprint was focused on finishing, tidying, documenting and getting an initial release out!


As a core building block of the Plone Intranet solution, ploneintranet.workspace aims to provide a flexible team / community workspace solution, allowing teams of users to communicate and collaborate effectively within their own area of an intranet. Plone’s extensive permissions are distilled into a set of distinct policies that control who can access a workspace, who can join a workspace, and what users can do once they are part of a workspace.

An Intro to Workspace Policies

Three realms of access are controlled via a single ‘policies’ tab on the workspace container:

External visibility

Who can see the workspace and its content?

  • Secret
    Workspace and content are only visible to members
  • Private
    Workspace is visible to non-members
    ‘Published’ Workspace content only visible to members
    ‘Public’ Workspace content visible to all
  • Open
    Workspace is visible to non-members
    ‘Published’ Workspace content visible to all

Join policy

Who can join / add users to a workspace?

    • Admin-managed
      Only workspace administrators can add users
    • Team-managed
      All existing workspace members can add users
    • Self-Managed
      Any user can self-join the workspace

Participation policy

What can members of the workspace do?

  • Consumers
    Members can read all published content
  • Producers
    Members can create new content, and submit for review
  • Publishers
    Members can create, edit and publish their own content (but not the content of others)
  • Moderators
    Members can create, edit and publish their own content and content created by others.

Policy Scenarios

These policies are designed to be combined in ways that produce sensible policy scenarios. Some example use cases might be:
  • Open + Self-managed + Publishers = Community/Wiki
  • Open + Admin-managed + Consumers = Business Division/Department
  • Private + Team-managed + Publishers = Team

Give it a try!

We would love you to try this package out and give us your feedback. For more information including how to download and install, see the documentation at

Further reading:

Tweet about this on TwitterShare on FacebookShare on Google+