Ticket #9578 (closed PLIP: wontfix)
Add new "Novice User" and "Site Administrator" roles
Reported by: | dukebody | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | General | Version: | 4.2 |
Keywords: | Cc: | servilio |
Description
http://plone.org/products/plone/roadmap/249
Plone would better protect new users and site admins by offering two roles that offer more limited powers.
Proposed by
Jon Stahl
Seconded by
Alex Limi
Proposal type
Architecture
State
being-discussed
Definitions
Motivation
Here at ONE/Northwest, we've got over 150 non-technical client organizations managing sites. Plone's legendary ease-of-use is a big selling point for most of them. However, Plone could do a better job of protecting less experienced users from accidentally damaging their site content.
Assumptions
This PLIP assumes that we have implemented sufficiently granular control panel configlet permissions as described in PLIP 248.
Proposal
We believe this can be most easily accomplished with two new roles:
1) A "Novice User" role that gives extremely limited powers to add and edit content.
2) A "Site Admnistrator" role that gives most but not all of the powers of the Manager role.
Here are the details. Joe - "Novice User"
Persona: Joe is a typical staff person at a small/midsized Plone-using organization. Joe is responsible for maintaining one or more sections of a Plone site, but is not the primary "website responsible person" in his organization. He's received basic training in Plone, but has not have mastered some of Plone's more advanced features, and occasionally makes mistakes. He'd like to be able to use Plone to add and edit content without fear of accidentally deleting something or changing the view of a page. His site admins would like that too, since they'd sleep a little better. Things Joe should be able to do
- Add new content
- Edit existing content
Things Joe should not be able to do
- Delete content
- Move content (requires delete permission)
- Use sharing tab
- Use "actions" menu
- Use "display" menu to change the layout/view on a content object
- Access the Plone control panel
- Add keywords
Jane - "Site Administrator"
Persona: Jane is the "website responsible person" for a small/midsized Plone site. She's not a developer, or even an integrator, but coordinates with other people who play those roles. She is responsible for supervising the content creation and editing process. As such, she needs to be able to administer all of the content management aspects of her Plone site, but should not be able to do access things that assume system administration or Plone integrator/developer skills. Things Jane should be able to do
- Generally, do all things that a Manager can do, except...
Things Jane should not be able to do
- Use the "Maintenance" control panel.
- Get to the ZMI
- Add/remove products
- Change themes
- Change cache configuration
Implementation
Deliverables
Risks
Progress log
Participants
Change History
comment:2 Changed 6 years ago by limi
- Component changed from Unknown to Infrastructure
- Milestone changed from Future to 4.x
Is this something that could be a candidate for 4.x releases?
comment:4 Changed 5 years ago by rossp
- Status changed from new to closed
- Resolution set to wontfix
PLEASE READ THIS AND RE-OPEN VALID PLIPS!
As we launch the new PLIP process we'd like to see which PLIPs:
- are still appropriate/needed
- still have owners/proposers/champions
- still have available implementers
If this PLIP should still be considered for future releases of Plone please do re-open this ticket and assign an appropriate milestone. If it should be considered for the next release of Plone, use the 4.2 milestone. Also be sure to update the PLIP description, requester, owner, etc. and include a comment detailing recent progress and new plans. We will use all these details in the new continuous PLIP process.
The Plone 4 framework team considered this proposal in #9312 and was generally in favor of the change, but it didn't go anywhere since no one stepped forward to implement it.