-
Book Overview & Buying
-
Table Of Contents
-
Feedback & Rating
Plone 3 Products Development Cookbook
When dealing with applications security, it is often wiser to give power to groups instead of users. Why is this? Because groups let us add or remove users as they come and go to a certain position or responsibility in an organization, which is reflected in the group itself.
In this way, if new people join the editors' crew of our website, then we can add their member IDs to the matching Editors' group in Plone and they will automatically have all their required roles and permissions.
On the other hand, if our security strategy were based on plain users, we'd have to manually add or remove every role to each and every member. In addition, there's no way in Plone to list all members for a specific role, so it would be difficult to know who can do what.
Furthermore, there is also a significant performance advantage when local roles are involved: adding a local role to a folder re-indexes the entire folder tree, which can be extremely costly if we added several users. On the...
Change the font size
Change margin width
Change background colour