Users, Authentication, and Permissions
-
-
Adding a custom permission to a product
-
Using rolemap.xml to create new Roles is easy, you can add predefined permissions to your new roles. But what if you want to define a new permission for your product? Use setDefaultRoles.
-
Create different restricted areas in the Control Panel
-
Here we describe how to programatically protect different elements of the Plone Control Panel with different permissions, so you can grant e.g. access to the Calendar configlet but not to the Add-ons one.
-
Hardening Plone
-
This document describes how to secure your Plone site. It is based on a use
case of a high-security project, that has been audited by professional security auditing companies. Both companies have approved the Plone site and
underlying infrastructure. The implementation was granted a certificate from certifiedsecure.eu.
-
Login Redirect Problems from Bad ACTUAL_URL
-
When you're prompted to log in to access something on your site, your redirect doesn't work and you have VirtualHost stuff in your ACTUAL_URL
-
Setup a Plone 3 site with public and restricted content
-
A relatively simple scheme for setting up your Plone 3 site with public (ie. anonymous), member, and restricted access.
-
Understanding permissions and security
-
Plone uses a combination of low-level Zope permissions, roles, local roles and workflows to manage permissions on objects. Understanding these will help you manage how, and by whom, your Plone site is accessed.
-
Adding a "Sharing" action-tab to your product/type
-
Two methods for adding a "Sharing" action-tab to your Plone product or item type.
-
Adding new roles to the Sharing Page
-
Explains how to add other roles to the set of managed roles at Plone 3 sharing tab.
-
Allowing Anonymous Users to Add Content
-
I had the need for Anonymous Plone users to add, edit, and save a specific content type in a specific location (folder) and couldn't find any resources, thus this quick HowTo.
-
Anonymous adding of unpublished content
-
This howto is about customizing an archetype content to let anonymous users add content, but not be able to view what has already been added.
-
Creating a private Plone site
-
How to make your site only accessible to logged-in users.
-
Enable editing for anonymous users under certain conditions
-
Sometimes due to convenience it is necessary allow content editing for anonymous users. One use case is allow anonymous review and feedback in certain workflow states. This how to explains how this can be achieved.
-
Ensure that deleted users can not re-register and gain control of their previouis folders
-
You may want to be able to delete naughty users from your site, but keep any content they may have created... However, default behaviour allows the users to re-register with the same user name and regain their existing folder. This fix stops that...
-
Grant Collection (ATTopic) permissions to contributors and editors
-
Out of the box, contributors and editors do not have the rights to manage Collections (topics, smart folders). This howto provides a genericsetup rolemap that makes Collections manageable just like other content.
-
Listing all permissions in the site
-
In the ZMI's "Security" tab, at the top level, you will see a list of all permissions in the site, and who has access to them. This how-to describes how to get a script to make a list of these permissions.
-
Removing things from the portal view for anonymous visitors
-
How to remove some features from the default "home page" view of your portal for anonymous visitors - but ensure they reappear once logged in.
-
Resetting User Passwords through Plone Interface (not ZMI)
-
So that you don't have to expose/subject your site adminstrators to the Zope Management Interface in order to reset user passwords, this How-To explains the process of resetting a user password by using the Plone (Site Setup) interface only.
-
Sharing Editing Capabilities for Pages and Folders
-
This describes how to give a user of your site editing privileges of particular folders or pages.
-
Show or hide a tab based on IP address
-
Shows you how to show or hide a portal tab based on the client IP address. Useful for intranet environments.
-
Setup a Plone 3 site with public and restricted content
-
A relatively simple scheme for setting up your Plone 3 site with public (ie. anonymous), member, and restricted access.
-
Adding user input into a Workflow
-
(this may have been abandoned)
-
Change state recursively in a workflow transition
-
When transitioning a folderish object, transition all children objects automatically.
-
Creating objects with workflow state of parent object
-
In this how-to one possible solution is shown for how to set newly created objects to the state of their parent object.
-
Creating Workflows in Plone
-
This documentation explains the purpose of the DCWorkflow product and how to make use of it. DCWorkflow is a CMF Product for Zope, and Plone's workflows are built using it.
-
Disabling workflows site-wide
-
How to disable workflows if you don't need them for your site.
-
Displaying only published items in folder listings to anonymous users.
-
If you don't do this, Plone's folder listing option will display both visible and published items to anonymous users.
-
eMail upcoming events to plone group
-
a python script to notify all members of a Plone group of upcoming events via email
-
Enable editing for anonymous users under certain conditions
-
Sometimes due to convenience it is necessary allow content editing for anonymous users. One use case is allow anonymous review and feedback in certain workflow states. This how to explains how this can be achieved.
-
Fixing Workflow States (a real-life example)
-
When workflows get confused, content items get reset to the default state. If you have a backup or a QA server, you can restore the correct workflow states.
-
Implement edit-view modes
-
Make it possible for users to show and hide the editable border and content tabs from a standard Plone site.
-
Make a complete folder structure private
-
This how-to summarizes the steps needed to make all elements below a private folder private.
-
New workflows in Plone 3
-
Plone 3 ships with a set of new workflows giving site administrators more choices when managing the ways their users interact with site content.
-
Partitioning your site with different access rules using custom workflows
-
This How To explains the necessary steps to partition your site, using a custom workflow, so that the same content types have seemingly different access rules based on where the content is within the site.
-
Restricting access to transitions using groups
-
Use portal groups to decide who can perform certain transitions
-
Send announcements from workflow
-
Shows how to send email announcements to members when workflow states are altered.
-
Send emails to users to remind them of expiring content
-
To keep my site fresh, I have a workflow action that sets ExpirationDate to now + 31 days. This how-to shows a way to send emails in advance of the item expiring.
-
Send mail on a workflow transition
-
Shows how to send an email when a workflow transition is triggered, for example to notify content owners that their document has been rejected.
-
Setting permissions with workflow
-
Describes how to alter object permissions based on workflow states.
-
Sharing Editing Capabilities for Pages and Folders
-
This describes how to give a user of your site editing privileges of particular folders or pages.
-
Time based workflow transitions
-
How to make workflows to do something based on time
-
Workflow with multiple approvals required
-
A custom workflow that requires a number of approvals of a document for it to be published.