Access Control
With the introduction of the Widget Framework, Content Studio becomes a tool not only for writers and editors, but also for publication designers and layout experts. In some cases, the same people may be responsible for both kinds of work, but in most organisations (especially in larger ones) these jobs will be carried out by specialists.
Since the Widget Framework's templates are in fact sections, you can use the standard Content Engine access control mechanisms to enforce this division of labour. All you need to do is create separate user groups for editorial and design staff, and then assign them different section-level access rights. You might, for example, assign the following access rights:
-
Design staff:
editor
orjournalist
access to templates (theconfig
section and its subsections),reader
access to content sections. If you are using separate publications for maintaining your sites and their design configuration, your design stuff should be giveneditor
orjournalist
access to the blueprint publications andreader
access to the site publications. -
Editorial staff:
editor
orjournalist
access to content sections, no access to templates. If you are using separate publications for maintaining sites and configuration, editorial stuff should be giveneditor
orjournalist
access to the site publications, and no access to blueprints.
You can, of course, specify access rights in more detail, creating sub-groups of designers with greater or lesser access to different templates, and give some individuals specialised access rights.
For a detailed description of Content Engine access control and how to use it, see Editing Users and Persons in the Escenic Content Engine Publication Administrator Guide.