Ticket #11240 (closed PLIP: wontfix)

Opened 5 years ago

Last modified 5 years ago

Plone Control Panel for all

Reported by: sauzher Owned by: limi
Priority: n/a Milestone: 4.x
Component: User Experience and Interface Version:
Keywords: Cc:

Description

Proposer: Alessandro Ceglie 'SauZheR'
Seconder: None as yet

Motivation

You can create a configlet C
You can share (create) a role R to access that configlet
You grant role R to user A.
User A can not access to configlet C because plone-control-panel is secured by Manage Portal permission only.

This applies to existing functionality too. Ex:
I can share the "manage users/groups" permission with someone and I must provide a link to access all users/group related views. Cause site setup is off limits for him.

Assumptions

A site Administrator (manager) should be able to delegate some portal-wide administrative functionality to some user/group without give him/them the Manage Portal permission.

Proposal & Implementation

I don't know the best way to implement this.
I suppose it should be easy to give more granular permission to default plone configlets and give a less restricting guard to site-setup view.

May be would be nice to move plone-control-panel to a browser view.

Deliverables

Review some browser view zcml registration. Move plone-control-panel into browser view machinery.

Risks

May be this plip overlaps with #10878 but consider the different point of view.

Participants

Me

Progress

None yet.

Change History

comment:1 Changed 5 years ago by sauzher

  • Summary changed from Plone Contro Panel for all to Plone Control Panel for all

comment:2 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.

Note: See TracTickets for help on using tickets.