Who does what in your CMS? What user should be allowed to edit templates or to approve edits? Each system has subtleties in permissions repartition and profiles naming, but basically there are only a few roles: technical administrator, functional administrator, website/section editor, contributor and reviewer.
They can be combined in different ways, one user profile may merge several roles. Just as in a family…
The Family
The Mother
Technical Administrator actually sets up the Content Management System and ensures it is properly running. Also known as Superuser, Technical Administrator is the primary user able to create new ones and set up permissions for them. He/she can access any part of the CMS. On a daily basis, Superuser will monitor application running, stop and restart it whenever needed.
The Father
Functional Administrator is the actual content manager. This user gets highest permission level regarding content creation and publishing: templates development, workflows management, pages set up, publication approval. Functional Administrator also manages users groups to make happen processes defined at organisation level.
The Uncle
Website / Section Editor is a content expert and liable of quality of content he/she is in charge of. He/she rules content creation process inside a definite website or section: can initiate a new workflow, may alter template at local level, check work in progress, send new page versions live.
The Child
Contributor duty is to prepare content: create a new page, edit an existing one, ask for his/her editions approval. His/her action may be initiated when notified of a workflow in progress. Basically, Contributor will focus on text editor and won’t have to access any other part of the application.
The cousin
Reviewer does not create content but will review content quality and most often metrics: how many articles published in a month, productivity for one specific user, or any figure set up in the system. Review role is often handled by Managers or Chief Editors.
Examples
Below are figures of two possible implementations of users roles repartition.
Figure 1
Figure 2
Figure 1 shows one where technical and functional administration are handled by a single user, and only one editor is required to overview the whole website. This is a configuration for a rather small website. Figure 2 is a classical configuration for large websites, when overall site has to be broken down in several sub-sections, each one overviewed by a specific editor. Of course there are other possibilities, even if all of them can’t be described here, let me know if you feel one should really be.
Whatever configuration you go for, never forget that it should reflect organisation processes. If you’re not happy with existing processes, start a change project to improve them before you implement them in the CMS. There is no hope to change existing processes just in implementing new roles in a Content Management System.
A folksonomy is the result of collaborative tagging of pieces of content (websites, photos, etc.), made by users using only their perception of the content and their immediate need of it. As folksonomies don’t rely on any established list of tags (or keywords), they are opposed to traditional classifications named ‘taxonomies’ or ‘ontologies’. The visual representation of folksonomies are 
