What is a Power User?

Hi

Interwoven charged us for "Power Users" on our last bill. Does anyone know what a Power User actually is? It doesnt really equate to any TS role and we are a bit sceptical as to what this actually is?

Any comments appreciated,

thanks,

- mark

Find more posts tagged with

Comments

Adam Stoller

I believe it applies to any role higher than an Author (i.e. Editor, Admin, Master)

However - if you really want to be sure - talk to your Interwoven Sales Representative.

--fish
(Interwoven Senior Technical Consultant)

Edited by ghoti on 01/22/03 04:54 AM (server time).

tvaughan

I had a nice long discussion with 3 different people at Interwoven. Your sales rep may tell you that a "Power User" is anyone found in the editor, admin or master UID files, but that doesn't jive.

Many TFO users must exist in the editor.uid file, but don't do anything more than act as 'authors'.

This is text from an Interwoven document mailed to me that describes a "power user" based on how they use TeamSite. Which, while more ambiguous, certainly is more fair.

User Roles within TeamSite

TeamSite Users:

Power User: A power user is more of a pricing term. In the TeamSite System a power user is sub-classified into 3 roles: Editor, Administrator and Master.

Editors own workareas. They create and edit content, just as Authors do, but they are primarily responsible for managing the development taking place within their workareas and submitting that content to the staging area as it becomes ready for the production environment. Editors can also have access to specialized TeamSite content and workflow management functions. Editors can select from a variety of workflows to assign an asset to an appropriate author.

Administrators own branches. They have all the abilities of Editors, but they are primarily responsible for the content and functioning of their branches. Administrators can manage projects by creating new workareas for Editors and groups, and by creating sub-branches of their own branches to explore separate paths of development.

Masters own the Web site from which all sub-branches are created. The Master can perform all the functions of Editors and Administrators on any branch. The Master is generally involved in the installation, configuration, and administration of TeamSite.

Authors own website content. They are primary content creators with limited access to the TeamSite system. They receive assignments from Editors, which are displayed in To Do lists when Authors log in to TeamSite. Authors can access TeamSite from a simple browser-based interface, and do not need to be sophisticated computer users. To test and QA their work, Authors have full access to the content in their Editors' workareas, but do not need to understand the larger structure and functionality of TeamSite. They Author role is appropriate for non-technical users, or for more technical contributors who do not need access to TeamSite's extended functionality.

Front-Office users are casual contributors. They are only allowed to contribute content to TeamSite through TeamSite Front-Office. They are allowed to contribute to only one workarea and only to one workflow. An editor is responsible for approving their work.

Reviewers are non-technical business managers. They are the primary users of WebDesk interface. Reviewers can participate in workflow approval processes only. They can approve the work of an author or editor, but they are not allowed to directly edit or submit content to TeamSite.

MASTER users own the website. They can perform all the functions of Editors and Administrators on any branch. The Master user owns the main branch, from which all sub-branches are created. The Master user is generally involved in the installation of TeamSite, and can reconfigure TeamSite on a system-wide bases.

ADMINISTRATORS own branches. They have all the abilities of Editors, but they are primarily responsible for the content and functioning of their branch. Administrators can manage project workflow by creating new workareas for Editors and groups, and be creating sub-branches of their own branch to explore separate paths of development.

An Administrator is the supervisor of the project being developed on his/her branch. For example, an Administrator might be the webmaster for a particular version of the website, or a project manager.

EDITORS own workareas. They create and edit content, just as Authors do, but they are primarily responsible for managing the development taking place within their workareas. This includes assigning files to Authors and submitting completed content to the staging area, and it might include publishing editions.

Editors have access to specialized TeamSite content and workflow management functions. Editors are generally either "managerial" users, who supervise the work of Authors, or self-managing "power" users, who need TeamSite's extended functionality to manage their own content.

AUTHORS own website content. They are primary content creators with limited access to the TeamSite system. They receive assignments from Editors, which are displayed in To Do lists when Authors log in to TeamSite. Authors can access TeamSite from a simple browser-based interface, and do not need to be sophisticated computer users. They can utilize any tool to create or edit content.

To test and QA their work, Authors have full access to the content in their Editors' workareas, but do not need to understand the larger structure and functionality of TeamSite. They Author role is appropriate for non-technical users, or for more technical contributors who do not need access to TeamSite's extended functionality.

FrontOffice users. Are casual website contributors, they are only allowed to contribute content to the website and cannot participate in workflows. They are allowed to contribute to only one workarea and only to one workflow. An editor is responsible for approving their work. They utilize standard office tools (word, excel and power point etc.) to contribute content.
.

Hope that helps,
Tom

Migrateduser

FrontOffice user is actually a bit more powerful than your typical author although the interface is deceiving. The typical author can only edit/add content but cannot do a GetLatest. With TFO users, you have that capability as well as delete.

- Max
mchwang@yahoo.com