‘Workbench’ helps to define who should do what to manage content on a site.
In any organisation, there is the inevitable issue of who should manage content on the website. There are concerns about the authenticity of the information, and accountability for the content displayed on the site. In many cases, organisations do not mind delaying making information available since they are very averse to inappropriate content showing up on their site.
By GHIDuOt, you FDn FontUoO DFFHss Ey GHfining UoOHs. Those in a particular role may have access rights to a content type. This is generally too restrictive an option. The same content type may be used across the organisation, but rights may depend on the actual content. As expected, there are a number of modules available for Drupal 7 that address certain aspects of this concern. The module that you may finG YHUy usHIuO is WoUNEHnFh (http://drupal.org/project/ workbench). ,t Fonsists oI IouU DGGitionDO PoGuOHs. WH will discuss the access and moderation modules, which are especially useful and relevant in most instances. on the site. To meet this need, the alternative taxonomyEDsHG PHFhDnisP oIIHUHG Ey WoUNEHnFh AFFHss is D IDU EHttHU oStion. You GHfinH D hiHUDUFhiFDO tDxonoPy, YHUy PuFh like a menu, using the Structure => Taxonomy option in the administrative menu. You need to worry only about the SDUHnt-FhiOG UHODtionshiS in thH GHfinition oI thH tDxonoPy, and not about the type of content each node represents.
Once the taxonomy is created, you can enable the WoUNEHnFh AFFHss PoGuOH DnG DssoFiDtH thH nHwOy FUHDtHG taxonomy with it. Each term in the taxonomy becomes a Section to EH PDnDgHG Ey WoUNEHnFh AFFHss. You nHHG to make sure the content types you want to be managed by access control are enabled.
The next step is to associate editors with each section— that is, you add those users for each section, who are permitted access to the corresponding section. Now, when users try to add content, they can only do so in a section for which they have rights and nothing more.