you@web Content Manager
 How is the system technically protected against access from others?
With you@web it is possible to use all security mechanisms of the Lotus Domino/Notes ar-chitecture. Thus a security concept is available which meets high standards like, for instance, the requirements in the military field. Access rights can be assigned to editorial teams, and on the website right down to document level. Are there pre-defined groups within a role concept?
Yes. In the you@web Content Manager different roles do exist, e.g. authors or approvers. Persons can be pooled into groups. The you@web Content Manager is directly based on the user administration of Lotus Domino/Notes.
Detailed user rights do exist. In complex Repository databases, for instance, Notes author fields and special roles in all layout documents of the Repository allow for a responsibility as-signment based upon user rights.
In regard to authors, restrictions for content creation can be defined for any content ranges or Website Areas ("Access Control" is only available for a role). In a Content Folder or a Web-site Area (navigation area) it is possible to define rights for creating documents - folders or content - on the lower levels individually by persons, groups, and roles. Can the groups within a role concept be freely defined?
Yes. Groups of persons as well as individuals can be used in the workflow. Which kinds of notification to individual employees does the system know?
Employees are informed by e-mail about tasks to be dealt with, e.g. the approval of a con-tent. It is possible to send mails including links (Notes + Web Link) and personal comments directly from content folders and content documents. Since in practice mail alone has often turned out to be ineffective (mails frequently reach the addressee at an unfavourable time), approval steps may also be processed via personalized views. Is there an authorisation cycle which is defined or can be freely organised for publications on the website?
The you@web Content Manager is equipped with a high performance workflow engine. It al-lows for n-level workflows with parallel and serial approval steps.
Furthermore, the workflow engine offers the following options:
· Direct approval by special persons (roles dependent)
If the author is at the same time an approver of the first workflow level, he can give his approval directly when submitting the document to the workflow.
· Content dependent workflow
Depending on the content, the workflow deposited in the Content Type may be ignored and a special workflow will be used (e.g. an input mask for events includes a general workflow, but depending on the venue other workflows will be used).
· Stand-in regulation
For each worklfow level a stand-in (or a group) can be defined together with a deadline.
· Workflow Supervisor
The Workflow Supervisor can always finalize the current workflow level and thus approve it, no matter whether he is specified in the respective workflow level or not.
· Workflow Level Supervisor
Depending on the settings, the Workflow Level Supervisor may approve all workflows, specific workflows, or specific workflow levels.
· Re-submission
An e-mail is sent as a reminder to the respective authors (definition in the content).
The individual approval steps are passed on by Notes mail including the Doc.-link, or by Internet mail including the URL-link. It is possible to add personal comments for the next edi-tor via a dialogue.
Since in practice mail alone has often turned out to be ineffective (mails frequently reach the addressee at an unfavourable time), approval steps may also be processed via personalized views. For each Content Type a different approval workflow may be defined. Is there a protection against inadvertent simultaneous access of several people to one document?
Concurrent working on a document is administered and supported by the Lotus Notes architecture by standard. Which kinds of system-internal task lists and status information are there?
Content Overviews are offered in different variants: Folder by Area, Document by Status, Content Overview, or Content by Content Type. Additionally, there are different workflow as well as administration views. [Basic information] [Asset managament] [Availabilty] [Content syndication] [Expandable] [Import] [Performance] [Personalisation] [Reports] [Workflow] [XML] | 
Update this entry
Downloads
