Plone User Accounts, Roles, Workflow and Publication
Status: I will not finish this page; see Update below.
Pagecode: T->1 A->SAml H->trsa[t,a,si,di]d[t,a,si,di] C->SA[cccej]
Last changed: Monday 2010-03-01 [12:22 UTC]
Abstract:
Plone websites come in many flavors, ranging from personal websites with one user to community, organization, or business websites that could have thousands of users. Each person who adds content to a Plone website has their own user account. A user account includes a user name and a password. Some Plone sites allow people to sign up by visiting the site, clicking a Join link, and filling out basic user information. Other sites have user accounts that are created by website administrators, in which case people normally receive emails with the user account details. However created, a Plone user account allows a person to log in by typing their user name and password. This user authentication is the foundation for roles and roles management. Each user gets a role assigned which determines his permissions in a very fine-grained manner e.g. one might be able to add and publish content but another user might just be able to add content but not to publish it (at that point it is added to the website but cannot be seen from the Internet for ordinary website visitors) -- he might then wait for approval of some other user (maybe his superior) which has higher permissions so he can publish the added content simply by clicking a button after he reviewed it.
|
Table of Contents
|
Update: I now (May 2009) stopped working with/on Plone in favor of
Dolmen simply because working with Plone is no fun anymore. Plone has
become way to fat and confusing to work with over the years — I need
something that works with me, not against me.
User Accounts
Anonymous Web Surfing
Authenticated Web Surfing
User Roles
Workflow
A workflow policy, sometimes abbreviated to workflow, describes the
constraints on state-changing actions for different groups of people.
Once the workflow policy has been created, it needs to be applied to
an area of the website for the rules to take affect.
Configuring a workflow policy is a matter of applying it to an area of
the website — to define the scope of the workflow. This is a website
administrator task. The website administrator would use control
panels of Plone to specify where on the website the Editorial Review
Policy applies, site-wide or to a subsection.
Plone comes with several useful workflow policies — the default one
is a simple web publishing policy. Our website administrator might
employ a more specific policy, such as a policy for a community-based
website or a company Intranet (internal web system). If so, you may
need to learn some procedural steps to publishing, but these are just
elaborations of principles in the default, basic workflow policy.
Right now (February 2008) there are three different out of the box
workflows we might choose. Two of them are so-called action-based
workflows (AlphaFlow and OpenFlow). The third one which also happens
the be Plone's default workflow is called DCWorkflow.
State-based Workflow
DCWorkflow
Action-based Workflow
OpenFlow
AlphaFlow
http://plone.org/products/alphaflow
Publication
Collaboration
|
