Personal tools
You are here: Home Products Plone Roadmap #211: Enable dashboard to be locked down
Document Actions

#211: Enable dashboard to be locked down

Contents
  1. Definitions
  2. Motivation
  3. Assumptions
  4. Proposal
  5. Implementation
  6. Deliverables
  7. Risks
  8. Progress log
  9. Participants
by Laurence Rowe last modified December 11, 2007 - 12:32
Portlets may be registered to the dashboard for groups, this makes the dashboard useful even when users should not be able to modify their own dashboard
Proposed by
Laurence Rowe
Proposal type
User interface
Repository branch
elro-locked-down-dashboard
State
being-discussed

Definitions

 

Motivation

The dashboard is controlled by a single 'Portlets: Manage own portlets' permission for both view and editing. For my site I need to lock down the editing of a user's dashboard, but still display it to the user. The infrastructure lets me register portlets to groups, so a user's dashboard is constructed from their group membership.

Assumptions

 

Proposal

  • Protect the dashboard with a 'Portlets: View own portlets' permission, making this configurable. This would require creating a new permission in plone.app.portlets and setting it up in CMFPlone's rolemap.xml
  • Remove the default dashboard portlet registrations on creation of new users. These should be set for the AuthenticatedUsers group instead, presuming the portlet blocking UI comes to light.
  • If time allows, create a UI for setting dashboard portlets for groups.

Implementation

 

Deliverables

 

Risks

 

Progress log

Currently I've taken the simplistic approach locally and have made the changes so that the dashboard can be viewed with zope2.View. This means that the username always links to the dashboard and never the author page. These changes are completely contained in plone.app.layout

Participants

Laurence Rowe

Framework team vote

Posted by Andreas Zeidler at December 13, 2007 - 23:07
tentative +1 with respect to the migration and security issues mentioned in http://lists.plone.org/pipermail/framework-team/2007-December/001497.html

+1

Posted by Tom Lazar at December 14, 2007 - 21:21
seconding andi's comments

Framework team vote

Posted by Raphael Ritz at December 17, 2007 - 13:20
same here (see above)

Framework vote

Posted by Martijn Pieters at December 21, 2007 - 17:12
+1 with same comments.

Framework team vote

Posted by Danny Bloemendaal at December 22, 2007 - 15:56
+1

For any issues with the web site functionality, please file a ticket.

Please consult the policy on plone.org content if you want your content published on this site.

Servers and hosting by