h1: ewok users This guide discusses three general classes of ewok user: - _content creators_, who are typically permitted to create and edit content that relates directly to their job functions (perhaps press releases, or answers to support questions) - _content owners_ typically "own" various sections or whole sites or trees of content, and can edit and publish within those areas, and maintain complete control over who has permission to view, edit, and publish within these areas. - _webmasters_ or _site administrators_ are responsible for the overall management of the site's content, and typically develop and maintain standard page elements such as headers and footers used for HTML page wrapping, and develop other page elements as necessary using ewok's "metadata": metadata.html facility (which allows data to be attached to directories and files) and its "embedded perl (embperl)": embperl.html support (which provides the ability to insert arbitrary perl code at any point in a page). These roles may well overlap or vary in the real world. You might: - have one or more content creators and owners - decide that various content owners can each be responsible for the look-and-feel of their own areas and assign them templating permissions - restrict templating permissions only to a designer - have one person responsible for end-to-end site development. The idea to grasp here is that ewok provides a very flexible permissions model, in which different levels of user access can be granted or denied to files or trees of files, and look-and-feel can be maintained only by those with templating permissions which are independent of users' view/edit/publish permissions. As well as these user types, the _ewok administrator_ is responsible for the technical administration of ewok itself. The ewok administrator can perform user, content and template management tasks, but is not typically involved with such day-to-day site management and maintenance.